From: Michal Bella
Signed-off-by: michal
---
mk/rte.sharelib.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mk/rte.sharelib.mk b/mk/rte.sharelib.mk
index c0a811a..a315d98 100644
--- a/mk/rte.sharelib.mk
+++ b/mk/rte.sharelib.mk
@@ -45,7 +45,7 @@ sharelib: $(LIB_ONE) FORC
Attaching to the list does not work. If you want the code let me know it is
only about 5K in size.
On Oct 6, 2014, at 2:45 PM, Wiles, Roger Keith
wrote:
>
> On Oct 6, 2014, at 11:13 AM, Wiles, Roger Keith windriver.com> wrote:
>
>>
>> On Oct 6, 2014, at 10:54 AM, Ananyev, Konstantin > inte
On Oct 6, 2014, at 11:13 AM, Wiles, Roger Keith
wrote:
>
> On Oct 6, 2014, at 10:54 AM, Ananyev, Konstantin intel.com> wrote:
>
>>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
>>> Sent: Monday, October 06, 2014 3:54 PM
>>> To: Wiles, Roger Keith (Wind River)
>>> Cc
Hi Everyone,
When we enable kernel config CONFIG_DEBUG_SECTION_MISMATCH=y and compile DPDK
1.7 with 3.14.17 kernel + gcc 4.8.2, we got lots of warnings like these.
Do we have plan to fix them? If so, please advise on which version. Thanks.
== Build lib/librte_eal/linuxapp/kni
cut: /proc/versio
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Monday, October 6, 2014 3:45 PM
> To: Pattan, Reshma
> Cc: dev at dpdk.org; Richardson, Bruce
> Subject: Re: [dpdk-dev] [PATCH v3] distributor_app: new sample app
>
> On Mon, Oct 06, 2014 at 02:16:22PM +00
On Mon, Oct 06, 2014 at 04:57:02PM +0100, Sergio Gonzalez Monroy wrote:
> At least on kernels 3.15 or newer, DPDK build is broken for CLANG target.
> The issue is that the kernel build system sets the flags before including
> DPDK makefile and therefore assumes the incorrect compiler.
>
> Signed-o
---
mk/rte.module.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mk/rte.module.mk b/mk/rte.module.mk
index c4ca3fd..bd3c596 100644
--- a/mk/rte.module.mk
+++ b/mk/rte.module.mk
@@ -78,7 +78,7 @@ build: _postbuild
$(MODULE).ko: $(SRCS_LINKS)
@if [ ! -f $(notdir Make
At least on kernels 3.15 or newer, DPDK build is broken for CLANG target.
The issue is that the kernel build system sets the flags before including
DPDK makefile and therefore assumes the incorrect compiler.
Signed-off-by: Sergio Gonzalez Monroy
---
mk/rte.module.mk | 2 +-
mk/targ
On Oct 6, 2014, at 10:54 AM, Ananyev, Konstantin wrote:
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
>> Sent: Monday, October 06, 2014 3:54 PM
>> To: Wiles, Roger Keith (Wind River)
>> Cc: dev at dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH 2/2] Adding the routines
On Mon, Oct 06, 2014 at 10:49:46AM -0400, Neil Horman wrote:
> On Mon, Oct 06, 2014 at 11:52:31AM +0100, Sergio Gonzalez Monroy wrote:
> > As per the proposal, this patch set does:
> > - Remove CONFIG_RTE_BUILD_COMBINE_LIBS as a configuration option.
> > - For static library, build a single/combi
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
> Sent: Monday, October 06, 2014 3:54 PM
> To: Wiles, Roger Keith (Wind River)
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH 2/2] Adding the routines
> rte_pktmbuf_alloc_bulk() and rte_pktmbuf_free_bulk()
>
> On M
On Mon, Oct 06, 2014 at 03:50:38PM +0100, Wiles, Roger Keith wrote:
> Hi Bruce,
>
> Do I need to reject the for the new routines or just make sure the vector
> driver does not get updated to use those routines?
>
The new routines are probably useful in the general case. I see no issue
with hav
Minor helper routines to mirror the mempool routines and remove the code
from applications. The ixgbe_rxtx_vec.c routine could be changed to use
the ret_pktmbuf_alloc_bulk() routine inplace of rte_mempool_get_bulk().
Combined __rte_mbuf_raw_alloc_bulk into the rte_pktmbuf_alloc_bulk function.
Fixe
On 9/26/2014 2:36 AM, Chao Zhu wrote:
> iopl() call is mostly for the i386 architecture. In Power architecture.
> It doesn't exist. This patch modified rte_eal_iopl_init() and make it
> return -1 on Power. This means rte_config.flags will not contain
> EAL_FLG_HIGH_IOPL flag on IBM Power architectu
On Mon, Oct 06, 2014 at 05:34:13PM +, Pattan, Reshma wrote:
>
>
> > -Original Message-
> > From: Neil Horman [mailto:nhorman at tuxdriver.com]
> > Sent: Monday, October 6, 2014 3:45 PM
> > To: Pattan, Reshma
> > Cc: dev at dpdk.org; Richardson, Bruce
> > Subject: Re: [dpdk-dev] [PATCH
On Oct 6, 2014, at 3:54 AM, Thomas Monjalon
wrote:
> 2014-10-03 21:05, Wiles, Roger Keith:
>> I run into a problem with Clang report problem when I tried to add
>> another member to the static initializer of the following in file
>> ixgbe_rxtx_vec.c
> [...]
>> Then I removed the {} and it now b
Hi Bruce,
Do I need to reject the for the new routines or just make sure the vector
driver does not get updated to use those routines?
Thanks
++Keith
On Oct 6, 2014, at 3:56 AM, Richardson, Bruce
wrote:
>
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Beha
On 9/26/2014 2:33 AM, Chao Zhu wrote:
> The set of patches split x86 architecture specific operations from DPDK and
> put them to the
> arch directories of i686 and x86_64 architecture. This will make the adpotion
> of DPDK much easier
> on other computer architecture. For a new architecture, jus
> -Original Message-
> From: Neil Horman [mailto:nhorman at tuxdriver.com]
> Sent: Wednesday, October 1, 2014 5:08 PM
> To: Richardson, Bruce
> Cc: Pattan, Reshma; dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3] distributor_app: new sample app
>
> > > >
> > > > 1)I had sent v5 patch
On Mon, Oct 06, 2014 at 11:52:34AM +0100, Sergio Gonzalez Monroy wrote:
> Remove COMBINE_LIBS option and by default build:
> - CONFIG_RTE_BUILD_SHARED_LIB=y : both individual and combined libraries
> - CONFIG_RTE_BUILD_SHARED_LIB=n : single combined library
As previously discussed.,It would be bet
On Mon, Oct 06, 2014 at 04:01:33PM +0100, Sergio Gonzalez Monroy wrote:
> On Mon, Oct 06, 2014 at 10:49:46AM -0400, Neil Horman wrote:
> > On Mon, Oct 06, 2014 at 11:52:31AM +0100, Sergio Gonzalez Monroy wrote:
> > > As per the proposal, this patch set does:
> > > - Remove CONFIG_RTE_BUILD_COMBINE
Signed-off-by: Sergio Gonzalez Monroy
---
mk/rte.app.mk | 4 ++--
mk/rte.lib.mk | 8 +++-
mk/rte.sharelib.mk | 7 ++-
3 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/mk/rte.app.mk b/mk/rte.app.mk
index 5e00e67..e775ad7 100644
--- a/mk/rte.app.mk
+++ b/mk/rte.app.
Remove COMBINE_LIBS option and by default build:
- CONFIG_RTE_BUILD_SHARED_LIB=y : both individual and combined libraries
- CONFIG_RTE_BUILD_SHARED_LIB=n : single combined library
Signed-off-by: Sergio Gonzalez Monroy
---
config/common_bsdapp | 3 +--
config/common_linuxapp | 3 +--
mk/rte.l
Signed-off-by: Sergio Gonzalez Monroy
---
mk/rte.app.mk | 160 +-
1 file changed, 2 insertions(+), 158 deletions(-)
diff --git a/mk/rte.app.mk b/mk/rte.app.mk
index 34dff2a..5e00e67 100644
--- a/mk/rte.app.mk
+++ b/mk/rte.app.mk
@@ -60,164
Signed-off-by: Sergio Gonzalez Monroy
---
mk/rte.sharelib.mk | 12 +++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/mk/rte.sharelib.mk b/mk/rte.sharelib.mk
index c0a811a..73ce709 100644
--- a/mk/rte.sharelib.mk
+++ b/mk/rte.sharelib.mk
@@ -29,6 +29,8 @@
# (INCLUDING N
As per the proposal, this patch set does:
- Remove CONFIG_RTE_BUILD_COMBINE_LIBS as a configuration option.
- For static library, build a single/combined library.
- For shared libraries, build both individual/separated and single/combined
libraries.
- Link apps only against single/combined l
2014-10-03 21:05, Wiles, Roger Keith:
> I run into a problem with Clang report problem when I tried to add
> another member to the static initializer of the following in file
> ixgbe_rxtx_vec.c
[...]
> Then I removed the {} and it now builds. Is this a result of the
> changes to the mbuf structure
On Sun, Oct 05, 2014 at 07:37:11PM +0100, Nicol?s Pernas Maradei wrote:
> Hi,
>
> New in Patch v2:
>
> - Fixes an issue in eth_dev_start/stop where a single interface was always
> opened/closed even though pcap files had been selected for rx/tx streams.
> - The link_status was not being properly
On Mon, Oct 06, 2014 at 11:52:31AM +0100, Sergio Gonzalez Monroy wrote:
> As per the proposal, this patch set does:
> - Remove CONFIG_RTE_BUILD_COMBINE_LIBS as a configuration option.
> - For static library, build a single/combined library.
> - For shared libraries, build both individual/separat
On Fri, Oct 03, 2014 at 02:21:50PM -0700, Matthew Hall wrote:
> On Fri, Oct 03, 2014 at 03:15:46PM -0400, Neil Horman wrote:
> > With a single archive, you get everything you build even if you don't need
> > it.
>
> Right, I was trying to avoid that for people who specifically didn't want it,
>
On Mon, Oct 06, 2014 at 02:16:22PM +, Pattan, Reshma wrote:
>
>
> > -Original Message-
> > From: Neil Horman [mailto:nhorman at tuxdriver.com]
> > Sent: Wednesday, October 1, 2014 5:08 PM
> > To: Richardson, Bruce
> > Cc: Pattan, Reshma; dev at dpdk.org
> > Subject: Re: [dpdk-dev] [PA
On Sat, Oct 04, 2014 at 07:14:21PM +0100, Nicol?s Pernas Maradei wrote:
> Hi,
>
> You are correct, the parameters received in the driver are allocated in
> devargs_list (char *params variable). However, they already get strdup'd in
> rte_kvargs_parse(). This newly allocated string is part of kvlis
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Keith Wiles
> Sent: Sunday, October 05, 2014 12:10 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH 2/2] Adding the routines rte_pktmbuf_alloc_bulk()
> and rte_pktmbuf_free_bulk()
>
> Minor helper routine
Hi Guys,
I'm doing my development on kind of a cheap machine with no NUMA support...
but several years ago I used DPDK to build a NUMA box that could do 40 gbits
bidirectional L4-L7 stateful traffic replay.
So given the past experiences I had before, I wanted to clean the code up so
it'd work
34 matches
Mail list logo