[dpdk-dev] Updating bnx2x firmware

On 24 March 2016 at 19:03, Harish Patil wrote: > > > >Guys, > > > > Currently, the bnx2x.c driver looks for the following firmware files > >(when > >PMD is enabled for it): > > > >--- > >$ ~/sources/dpdk/dpdk-2.2.0/drivers/net/bnx2x$ grep lib\/firmware * > >bnx2x.c:#define FW_NAME_57711

[dpdk-dev] [PATCH] mk: show version as a decimal integer

In order to ease packaging support of changes in DPDK build system, introduce a decimal integer to compare version numbers. It does not show the minor numbers as it is not meaningful for packaging. Usage for DPDK 16.04: % make showversionum 1604 Signed-off-by: Thomas Monjalon ---

[dpdk-dev] [PATCH] scripts: improve quiet checkpatch

2015-12-13 03:37, Thomas Monjalon: > The option --no-summary will remove this line in quiet mode: > total: 1 errors, 0 warnings, 7 lines checked > > Signed-off-by: Thomas Monjalon Applied

[dpdk-dev] [PATCH] scripts: fix checkpatch help

2016-02-16 15:36, Olivier Matz: > When started without defining DPDK_CHECKPATCH_PATH, the usage was not > displayed. > > Signed-off-by: Olivier Matz Applied, thanks

[dpdk-dev] Updating bnx2x firmware

> >Guys, > > Currently, the bnx2x.c driver looks for the following firmware files >(when >PMD is enabled for it): > >--- >$ ~/sources/dpdk/dpdk-2.2.0/drivers/net/bnx2x$ grep lib\/firmware * >bnx2x.c:#define FW_NAME_57711 "/lib/firmware/bnx2x/bnx2x-e1h-7.2.51.0.fw" >bnx2x.c:#define FW_NAME_57810

[dpdk-dev] [PATCH 0/2] tools/setup.sh fixes

2016-03-14 17:45, Jerin Jacob: > - added support to work with systems other than 2MB page size > - added support to work with built-in kernel modules > > > Jerin Jacob (2): > tools/setup.sh: remove 2MB huge page size hard-cording > tools/setup.sh: Support built-in kernel modules Applied,

[dpdk-dev] [PATCH v2] tools/dpdk_nic_bind: fix flake8 warnings

> > flake8 checks were run for both python 2.7 and 3.4 > > > > There were some style issues as: > > - Line width > 79 > > - No double blank line before function definition > > - No double blank space before inline comment > > - Some other minor issues > > > > Signed-off-by: Mauricio Vasquez B >

[dpdk-dev] [PATCH] Remove the extra blank lines in the output

2015-12-08 12:52, Keith Wiles: > The output for the core list included an extra linefeed making > the number of lines displayed much larger then required. > > Signed-off-by: Keith Wiles Applied, thanks

[dpdk-dev] [PATCH] autotests: fix pmd ring

2016-03-15 13:25, Olivier Matz: > This test expects that a vdev is instanciated on the command > line. If it's not the case, just skip this part. > > Signed-off-by: Olivier Matz Applied, thanks

[dpdk-dev] [PATCH] autotests: display command line when starting

2016-03-15 13:25, Olivier Matz: > It's useful for debug purposes to see the command line used by > autotest.py. > > Signed-off-by: Olivier Matz Applied, thanks

[dpdk-dev] [PATCH v2 0/3] Extend list of supported algorithms in L2fwd-crypto

2016-03-22 21:23, Pablo de Lara: > New cipher/authentication algorithms are supported in cryptodev, > so L2fwd-crypto needs to have the list of supported algorithms updated. > > Changes in v2: > - Added other two algorithms > - Modified offset and length in bits for SNOW3G algorithms > > Pablo

[dpdk-dev] [PATCH v2] l2fwd-crypto: fix incorrect command line help

> > Previous cdev parameter was changed to cdev_type, to select a crypto device > > type preference (HW/SW/ANY), instead of the device itself (QAT/AESNI...). > > Also deleted cdev duplicated parameter from the help. > > > > Fixes: 27cf2d1b18e1 ("examples/l2fwd-crypto: discover capabilities") > >

[dpdk-dev] Updating bnx2x firmware

Guys, Currently, the bnx2x.c driver looks for the following firmware files (when PMD is enabled for it): --- $ ~/sources/dpdk/dpdk-2.2.0/drivers/net/bnx2x$ grep lib\/firmware * bnx2x.c:#define FW_NAME_57711 "/lib/firmware/bnx2x/bnx2x-e1h-7.2.51.0.fw" bnx2x.c:#define FW_NAME_57810

[dpdk-dev] [PATCH 1/2] szedata2: new poll mode driver

D?a 21.03.2016 o 18:45 Stephen Hemminger nap?sal(a): > On Fri, 19 Jun 2015 10:25:00 +0200 > Matej Vido wrote: > >> +static struct ether_addr eth_addr = { >> +.addr_bytes = { 0, 0, 0, 0x1, 0x2, 0x3 } >> +}; > ... > >> static int >> rte_szedata2_eth_dev_init(struct rte_eth_dev *dev) >> { > ..

[dpdk-dev] [PATCH 2/2 v6] i40e: Add floating VEB support in i40e

This patch add the support for floating VEB in i40e. All the VFs VSIs can decide whether to connect to the legacy VEB/VEPA or the floating VEB. When connect to the floating VEB a new floating VEB is created. Now all the VFs need to connect to floating VEB or legacy VEB, cannot connect to both of

[dpdk-dev] [PATCH 1/2 v6] i40e: support floating VEB config

Add the new floating related argument option in the devarg. Using this parameter, all the samples can decide whether to use legacy VEB/VEPA or floating VEB. To enable this feature, the user should pass a devargs parameter to the EAL like "-w 84:00.0,enable_floating=1", and the application will

[dpdk-dev] [PATCH 0/2 v6] i40e: Add floating VEB support for i40e

This patch-set add the support for floating VEB in i40e. All the VFs VSIs can decide whether to connect to the legacy VEB/VEPA or the floating VEB. When connect to the floating VEB a new floating VEB is created. Now all the VFs need to connect to floating VEB or legacy VEB, cannot connect to both

[dpdk-dev] Question on examples/multi_process app

> > >> > >> >> -Original Message- >> >> From: Richardson, Bruce >> >> Sent: Wednesday, March 23, 2016 11:45 AM >> >> To: Ananyev, Konstantin >> >> Cc: Harish Patil; dev at dpdk.org >> >> Subject: Re: [dpdk-dev] Question on examples/multi_process app >> >> >> >> On Wed, Mar 23, 2016 at

[dpdk-dev] [PATCH v11 0/8] ethdev: 100G and link speed API refactoring

D?a 17.03.2016 o 19:08 Thomas Monjalon nap?sal(a): > There are still too few tests and reviews, especially for > autonegotiation with Intel devices (patch #6). > I would not be surprised to see some bugs in this rework. > > The capabilities must be adapted per device. It can be > improved in a

[dpdk-dev] [PATCH v3 0/4] arm: detect NEON by RTE_MACHINE_CPUFLAG_NEON flag only

2016-03-19 20:58, Jan Viktorin: > Hello, > > finally, I've broken the original patch into 4 pieces as it solves more issues > and not just a single one. > > * As Thomas have already mentioned, the CONFIG_RTE_ARCH_ARM_NEON is > confusing. > So, I've decided to remove it entirely and provide

[dpdk-dev] [PATCH v2] ixgbe: disable icc compile warning

> -Original Message- > From: Yigit, Ferruh > Sent: Thursday, March 24, 2016 5:35 PM > To: dev at dpdk.org > Cc: Stephen Hemminger; Ananyev, Konstantin; Yigit, Ferruh > Subject: [PATCH v2] ixgbe: disable icc compile warning > > icc (icc (ICC) 16.0.1 20151021) is generating following

[dpdk-dev] [PATCH v4 0/3] Fix incorrect max TX queue numbers for ixgbe

On Thu, Mar 24, 2016 at 05:44:58PM +, Bruce Richardson wrote: > On Thu, Mar 24, 2016 at 03:22:01PM +, Pablo de Lara wrote: > > IXGBE supports 128 TX queues. However, the full 128 queues > > are only available in VT and DCB mode. > > In normal default "none" mode (VT/DCB off) the maximum

[dpdk-dev] [PATCH v4 0/3] Fix incorrect max TX queue numbers for ixgbe

On Thu, Mar 24, 2016 at 03:22:01PM +, Pablo de Lara wrote: > IXGBE supports 128 TX queues. However, the full 128 queues > are only available in VT and DCB mode. > In normal default "none" mode (VT/DCB off) the maximum number > of available queues is only 64. > IXGBE doesn't check the mode when

[dpdk-dev] [PATCH v2] ixgbe: disable icc compile warning

icc (icc (ICC) 16.0.1 20151021) is generating following compile error: " CC ixgbe_rxtx.o .../drivers/net/ixgbe/ixgbe_rxtx.c(153): error #3656: variable "free" may be used before its value is set (nb_free > 0 && m->pool != free[0]->pool)) {

[dpdk-dev] [PATCH v2] l2fwd-crypto: fix incorrect command line help

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Thursday, March 24, 2016 1:40 PM > To: dev at dpdk.org > Cc: Doherty, Declan; De Lara Guarch, Pablo > Subject: [dpdk-dev] [PATCH v2] l2fwd-crypto: fix incorrect command line help > >

[dpdk-dev] [PATCH v4 3/3] ixgbe: fix incorrect max tx queue number

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Thursday, March 24, 2016 3:22 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo ; Richardson, Bruce > ; De Lara Guarch, Pablo > > Subject: [dpdk-dev] [PATCH v4 3/3] ixgbe: fix incorrect max tx

[dpdk-dev] [PATCH v4 2/3] ethdev: copy device configuration earlier

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Thursday, March 24, 2016 3:22 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo ; Richardson, Bruce > ; De Lara Guarch, Pablo > > Subject: [dpdk-dev] [PATCH v4 2/3] ethdev: copy device

[dpdk-dev] [PATCH v4 1/3] ixgbe: fix incorrect tx queue number assignment

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Thursday, March 24, 2016 3:22 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo ; Richardson, Bruce > > Subject: [dpdk-dev] [PATCH v4 1/3] ixgbe: fix incorrect tx queue number > assignment > >

[dpdk-dev] [PATCH] mempool: allow for user-owned mempool caches

On Mon, Mar 21, 2016 at 3:49 PM, Wiles, Keith wrote: >>Hi Lazaros, >> >>Thanks for this patch. To me, this is a valuable enhancement. >>Please find some comments inline. >> >>On 03/10/2016 03:44 PM, Lazaros Koromilas wrote: >>> The mempool cache is only available to EAL threads as a per-lcore >>>

[dpdk-dev] [PATCH] mempool: allow for user-owned mempool caches

Hi Konstantin, On Mon, Mar 21, 2016 at 3:15 PM, Ananyev, Konstantin wrote: > > Hi lads, > >> >> Hi Lazaros, >> >> Thanks for this patch. To me, this is a valuable enhancement. >> Please find some comments inline. > > Yep, patch seems interesting. > One question - what would be the usage model

[dpdk-dev] [PATCH v4 3/3] ixgbe: fix incorrect max tx queue number

From: Wenzhuo Lu IXGBE supports 128 TX queues. However, the full 128 queues are only available in VT and DCB mode. In normal default "none" mode (VT/DCB off) the maximum number of available queues is only 64. IXGBE doesn't check the mode when reporting the available number

[dpdk-dev] [PATCH v4 2/3] ethdev: copy device configuration earlier

In rte_eth_dev_configure(), device configuration was copied after requesting the device information, to check the maximum number of RX/TX queues. Since this number may change depending on the device configuration, the memcpy of it has to be performed before requesting the device information.

[dpdk-dev] [PATCH v4 1/3] ixgbe: fix incorrect tx queue number assignment

From: Wenzhuo Lu Internal variable containing the number of TX queues for a device, was being incorrectly assigned the number of RX queues, instead of TX. Signed-off-by: Wenzhuo Lu --- drivers/net/ixgbe/ixgbe_ethdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[dpdk-dev] [PATCH v4 0/3] Fix incorrect max TX queue numbers for ixgbe

IXGBE supports 128 TX queues. However, the full 128 queues are only available in VT and DCB mode. In normal default "none" mode (VT/DCB off) the maximum number of available queues is only 64. IXGBE doesn't check the mode when reporting the available number of queues. If a queue larger than 64 is

[dpdk-dev] [PATCH v3] ixgbe: add check for tx queue number

From: Wenzhuo Lu IXGBE supports 128 TX queues. However, the full 128 queues are only available in VT and DCB mode. In normal default "none" mode (VT/DCB off) the maximum number of available queues is only 64 (except for 82598EB, which is 32 for all modes). IXGBE doesn't

[dpdk-dev] [PATCH v2 2/2] igb: fix the wrong address of device data pointer

In the function set_rx_mode, the pointer of device data points to the wrong address as found in ixgbe code. Fixes: be2d648a2dd3("igb: add PF support") Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/igb_pf.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git

[dpdk-dev] [PATCH v2 1/2] ixgbe: fix the wrong address of device data pointer

There's an issue reported. In the scenario DPDK PF + DPDK VF, if the VF port is closed, PF port cannot receive packets. I found at that time the promicuous mode is disabled on the PF port. But it should be enabled. When VF port is closed, it will send a message to its PF port to reset it. During

[dpdk-dev] [PATCH v2 0/2] fix the wrong address of device data pointer

In the function set_rx_mode, the pointer of device data points to the wrong address. v2: - Remove the unnecessary cast. Wenzhuo Lu (2): ixgbe: fix the wrong address of device data pointer igb: fix the wrong address of device data pointer drivers/net/e1000/igb_pf.c | 3 +--

[dpdk-dev] [PATCH] mempool: allow for user-owned mempool caches

>On Mon, Mar 21, 2016 at 3:49 PM, Wiles, Keith wrote: >>>Hi Lazaros, >>> >>>Thanks for this patch. To me, this is a valuable enhancement. >>>Please find some comments inline. >>> >>>On 03/10/2016 03:44 PM, Lazaros Koromilas wrote: The mempool cache is only available to EAL threads as a

[dpdk-dev] [PATCH v2] i40e: fix ipv6 TSO issue for tx function

On Wed, Mar 23, 2016 at 11:27:50AM +0800, Zhe Tao wrote: > Issue: > when using the following CLI in testpmd to enable ipv6 TSO feature > = > set verbose 1 > csum set ip hw 0 > csum set udp hw 0 > csum set tcp hw 0 > csum set sctp hw 0 > csum set outer-ip hw 0 > csum parse_tunnel on 0 >

[dpdk-dev] [PATCH] bond: use existing enslaved device queues

This solves issues when an active device is added to a bond. If a device to be enslaved already has transmit and/or receive queues allocated, use those and then create any additional queues that are necessary. Fixes: 2efb58cbab6e ("bond: new link bonding library") Signed-off-by: Eric Kinzie

[dpdk-dev] [PATCH] mempool: allow for user-owned mempool caches

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Lazaros Koromilas > Sent: Thursday, March 24, 2016 7:36 AM > To: Wiles, Keith > Cc: Olivier Matz ; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] mempool: allow for user-owned mempool > caches > > On Mon,

[dpdk-dev] [PATCH v2] i40e: fix ipv6 TSO issue for tx function

On Wed, Mar 23, 2016 at 11:27:50AM +0800, Zhe Tao wrote: > Issue: > when using the following CLI in testpmd to enable ipv6 TSO feature > = > set verbose 1 > csum set ip hw 0 > csum set udp hw 0 > csum set tcp hw 0 > csum set sctp hw 0 > csum set outer-ip hw 0 > csum parse_tunnel on 0 >

[dpdk-dev] [PATCH 2/2] igb: fix the wrong address of device data pointer

In the function set_rx_mode, the pointer of device data points to the wrong address as found in ixgbe code. Fixes: be2d648a2dd3("igb: add PF support") Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/igb_pf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[dpdk-dev] [PATCH 1/2] ixgbe: fix the wrong address of device data pointer

There's an issue reported. In the scenario DPDK PF + DPDK VF, if the VF port is closed, PF port cannot receive packets. I found at that time the promicuous mode is disabled on the PF port. But it should be enabled. When VF port is closed, it will send a message to its PF port to reset it. During

[dpdk-dev] [PATCH 0/2] fix the wrong address of device data pointer

In the function set_rx_mode, the pointer of device data points to the wrong address. Wenzhuo Lu (2): ixgbe: fix the wrong address of device data pointer igb: fix the wrong address of device data pointer drivers/net/e1000/igb_pf.c | 2 +- drivers/net/ixgbe/ixgbe_pf.c | 2 +- 2 files

[dpdk-dev] [PATCH] hash: fix typo in Doxygen comment

rte_hash_set_cmp_func() had an incorrect Doxygen comment for one of its parameters. Fixes: 95da2f8e9c61 ("hash: customize compare function") Signed-off-by: Pablo de Lara --- lib/librte_hash/rte_hash.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[dpdk-dev] arch check in example dpdk_qat

2016-03-24 11:58, De Lara Guarch, Pablo: > > > -Original Message- > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > Sent: Thursday, March 24, 2016 11:01 AM > > To: De Lara Guarch, Pablo > > Cc: Richardson, Bruce; dev at dpdk.org > > Subject: Re: arch check in example

[dpdk-dev] [PATCH] hash: fix memcmp function pointer in multi-process environment

Hi, > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of ?? > Sent: Tuesday, March 15, 2016 1:03 AM > To: Dhananjaya Eadala > Cc: Richardson, Bruce; De Lara Guarch, Pablo; Qiu, Michael; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] hash: fix memcmp function

[dpdk-dev] [PATCH] hash: fix to support multi process

Hash library used a function pointer to choose a different key compare function, depending on the key size. As a result, multiple processes could not use the same hash table, as the function addresses vary from one process to another. Instead, a jump table is used, so each process has its own

[dpdk-dev] [PATCH v2] l2fwd-crypto: fix incorrect command line help

Previous cdev parameter was changed to cdev_type, to select a crypto device type preference (HW/SW/ANY), instead of the device itself (QAT/AESNI...). Also deleted cdev duplicated parameter from the help. Fixes: 27cf2d1b18e1 ("examples/l2fwd-crypto: discover capabilities") Signed-off-by: Pablo de

[dpdk-dev] [PATCH] l2fwd-crypto: fix incorrect parameter in help

> -Original Message- > From: Trahe, Fiona > Sent: Tuesday, March 22, 2016 3:08 PM > To: De Lara Guarch, Pablo; dev at dpdk.org > Cc: Doherty, Declan; De Lara Guarch, Pablo > Subject: RE: [dpdk-dev] [PATCH] l2fwd-crypto: fix incorrect parameter in help > > > > > -Original

[dpdk-dev] [PATCH] fm10k: conditionally disable RSS during device initialization

Jing, Thanks for your assistance. The experiment that you have built should allow you to observe the bug. In [5], I would expect that queue 0 receives roughly 1/4 of the packets that you sending, assuming the input packets have varied IP addresses. Can you measure what % of packets are actually

[dpdk-dev] [PATCH] mlx4: use dummy rxqs when a non-pow2 number is requested

Hi Bruce, On 03/24/2016 01:20 PM, Bruce Richardson wrote: >> @@ -734,12 +734,12 @@ dev_configure(struct rte_eth_dev *dev) >> } >> if (rxqs_n == priv->rxqs_n) >> return 0; >> -if ((rxqs_n & (rxqs_n - 1)) != 0) { >> -ERROR("%p: invalid number of RX queues

[dpdk-dev] [PATCH v2 0/2] fix the wrong address of device data pointer

On Thu, Mar 24, 2016 at 03:07:44PM +0800, Wenzhuo Lu wrote: > In the function set_rx_mode, the pointer of device data points > to the wrong address. > > v2: > - Remove the unnecessary cast. > > Wenzhuo Lu (2): > ixgbe: fix the wrong address of device data pointer > igb: fix the wrong address

[dpdk-dev] [PATCH] ixgbe: fix vector RX can't always set packet_type properly

On Wed, Mar 23, 2016 at 10:54:23AM +0800, Liang, Cunming wrote: > Hi, > > On 3/22/2016 10:30 PM, Konstantin Ananyev wrote: > >Fixes: 39625417585 ("mbuf: redefine packet type") > > > >Current vector RX can't always set packet_type properly. > >To be more specific: > >a) it never sets

[dpdk-dev] [PATCH] mlx4: use dummy rxqs when a non-pow2 number is requested

On Mon, Mar 21, 2016 at 05:08:04PM +0100, Olivier Matz wrote: > When using RSS, the number of rxqs has to be a power of two. > This is a problem because there is no API is dpdk that makes > the application aware of that. > > A good compromise is to allow the application to request a > number of

[dpdk-dev] [PATCH] mlx4: check if port is configured for Ethernet

On Tue, Mar 22, 2016 at 11:34:26AM +0100, Adrien Mazarguil wrote: > Notify user otherwise. A similar check has already been added to mlx5 in > commit "mlx5: check port is configured as ethernet device". > > Signed-off-by: Adrien Mazarguil > --- Applied to dpdk-next-net/rel_16_04 /Bruce

[dpdk-dev] Bug in i40e PMD for flexible payload

On Wed, Mar 23, 2016 at 01:44:46PM -0500, Michael Habibi wrote: > We are using the i40 implementation to configure flow director with > flexible payload rules. When setting up rules, it allows you to set a value > to 63 to disable the rule (NONUSE_FLX_PIT_DEST_OFF). However, the macro in >

[dpdk-dev] arch check in example dpdk_qat

2016-03-24 10:50, De Lara Guarch, Pablo: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > When reading examples/dpdk_qat/Makefile, we can see this check: > > > > ifneq ($(CONFIG_RTE_ARCH),"x86_64") > > ifneq ($(LBITS),i686) > > $(error The RTE_TARGET chosen is

[dpdk-dev] arch check in example dpdk_qat

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Thursday, March 24, 2016 11:01 AM > To: De Lara Guarch, Pablo > Cc: Richardson, Bruce; dev at dpdk.org > Subject: Re: arch check in example dpdk_qat > > 2016-03-24 10:50, De Lara Guarch, Pablo: >

[dpdk-dev] Question on examples/multi_process app

> > > >> -Original Message- > >> From: Richardson, Bruce > >> Sent: Wednesday, March 23, 2016 11:45 AM > >> To: Ananyev, Konstantin > >> Cc: Harish Patil; dev at dpdk.org > >> Subject: Re: [dpdk-dev] Question on examples/multi_process app > >> > >> On Wed, Mar 23, 2016 at 11:09:17AM

[dpdk-dev] [PATCH v2 0/5] virtio support for container

Hi Neil, On 3/24/2016 3:17 AM, Neil Horman wrote: > On Fri, Feb 05, 2016 at 07:20:23PM +0800, Jianfeng Tan wrote: >> v1->v2: >> - Rebase on the patchset of virtio 1.0 support. >> - Fix cannot create non-hugepage memory. >> - Fix wrong size of memory region when "single-file" is used. >> -

[dpdk-dev] arch check in example dpdk_qat

Hi Thomas, > -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, March 23, 2016 11:04 AM > To: Richardson, Bruce; De Lara Guarch, Pablo > Cc: dev at dpdk.org > Subject: arch check in example dpdk_qat > > When reading

[dpdk-dev] [PATCH 1/2 v5] i40e: support floating VEB config

On Wed, Mar 23, 2016 at 01:51:09PM +0100, Thomas Monjalon wrote: > 2016-03-23 20:27, Zhe Tao: > > Add the new floating related argument option in the EAL. > > Using this parameter, all the samples can decide whether to use legacy > > VEB/VEPA > > or floating VEB. > > Even the floating argument is

[dpdk-dev] [PATCH v2 0/5] virtio support for container

On Thu, Mar 24, 2016 at 11:10:50AM +0800, Tan, Jianfeng wrote: > Hi Neil, > > On 3/24/2016 3:17 AM, Neil Horman wrote: > >On Fri, Feb 05, 2016 at 07:20:23PM +0800, Jianfeng Tan wrote: > >>v1->v2: > >> - Rebase on the patchset of virtio 1.0 support. > >> - Fix cannot create non-hugepage memory.

[dpdk-dev] [PATCH v2 2/7] drivers/net/e1000: Fix missing brackets

On 03/24/2016 02:35 AM, Lu, Wenzhuo wrote: > Hi Thomas, Aaron, >>> Wenzhuo, do you agree to fix the base driver here? > Honestly I find the logic has some problem and maybe more changes needed. I'm > talking with our kernel driver contactors to make sure they have no concern > about my idea. >

[dpdk-dev] [PATCH v11 0/8] ethdev: 100G and link speed API refactoring

On 24 March 2016 at 07:21, Xu, Qian Q wrote: > Marc > > I didn?t quite get your points, I observed that after applying this > patchset, all intel nic can?t be started, maybe something wrong happened > when you check the duplex/autoneg value for different NICs. If we want to > merge the patchset

[dpdk-dev] [PATCH v2] ixgbe: add check for tx queue number

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pablo de Lara > Sent: Wednesday, March 23, 2016 3:29 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo ; De Lara Guarch, Pablo > > Subject: [dpdk-dev] [PATCH v2] ixgbe: add check for tx queue number > > IXGBE

[dpdk-dev] Suggestions for the dpdk stable tree

Hi, there is a stable tree for dpdk 2.2 at http://dpdk.org/browse/dpdk-stable/ But it is still at the 2.2 Release status. I was working on testing 2.2 and needed to pull in some patches from post 2.2 release to fix issues. After that I started to "scan" the git log what else might apply to a

[dpdk-dev] [PATCH v2] ixgbe: add check for tx queue number

Hi, I tested this patch with OVS+DPDK on a 72 lcores board with an Intel 82599ES 10 Gb NIC. It works fine. Now when I call 'rte_eth_dev_info_get()' it returns correctly the number of available Tx queues for the default mode, i.e. 64 when no VT and no DCB is set. Also, if I attempt to request

[dpdk-dev] [PATCH v2 2/2] igb: fix the wrong address of device data pointer

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wenzhuo Lu > Sent: Thursday, March 24, 2016 3:08 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo > Subject: [dpdk-dev] [PATCH v2 2/2] igb: fix the wrong address of device data > pointer > > In the function

[dpdk-dev] [PATCH v2 1/2] ixgbe: fix the wrong address of device data pointer

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wenzhuo Lu > Sent: Thursday, March 24, 2016 3:08 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo > Subject: [dpdk-dev] [PATCH v2 1/2] ixgbe: fix the wrong address of device > data pointer > > There's an issue

[dpdk-dev] [PATCH 1/2] ixgbe: fix the wrong address of device data pointer

Hi Jingjing, > > set_rx_mode(struct rte_eth_dev *dev) > > { > > struct rte_eth_dev_data *dev_data = > > - (struct rte_eth_dev_data*)dev->data->dev_private; > > + (struct rte_eth_dev_data *)dev->data; > Cast is unnecessary here. O, didn't notice that. Will send a V2.

[dpdk-dev] Question on examples/multi_process app

> > > > >> -Original Message- >> From: Richardson, Bruce >> Sent: Wednesday, March 23, 2016 11:45 AM >> To: Ananyev, Konstantin >> Cc: Harish Patil; dev at dpdk.org >> Subject: Re: [dpdk-dev] Question on examples/multi_process app >> >> On Wed, Mar 23, 2016 at 11:09:17AM +, Ananyev,

[dpdk-dev] [PATCH 1/2] ixgbe: fix the wrong address of device data pointer

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wenzhuo Lu > Sent: Thursday, March 24, 2016 2:37 PM > To: dev at dpdk.org > Cc: Lu, Wenzhuo > Subject: [dpdk-dev] [PATCH 1/2] ixgbe: fix the wrong address of device data > pointer > > There's an issue

[dpdk-dev] [PATCH] fm10k: conditionally disable RSS during device initialization

Hi, Frasca, > -Original Message- > From: Michael Frasca [mailto:michael.frasca at oracle.com] > Sent: Wednesday, March 23, 2016 9:43 PM > To: Chen, Jing D > Cc: dev at dpdk.org > Subject: Re: [PATCH] fm10k: conditionally disable RSS during device > initialization > > Hi Jing, > > I

[dpdk-dev] [PATCH v11 0/8] ethdev: 100G and link speed API refactoring

Marc I didn?t quite get your points, I observed that after applying this patchset, all intel nic can?t be started, maybe something wrong happened when you check the duplex/autoneg value for different NICs. If we want to merge the patchset in RC2, we need fix them. Maybe not an easy job in

[dpdk-dev] testpmd could not start up with vmxnet3 port

On 3/23/16, 8:55 AM, "Thomas Monjalon" wrote: >2016-03-23 05:57, Yong Wang: >> From: Ding, HengX >> > Testpmd will fail to start up with vmxnet3 port. >[...] >> Currently vmxnet3?s default_txconf.txq_flags is set to the following, which >> is used by testpmd >> as there is no explicit txconf

[dpdk-dev] [PATCH v3 00/10] qede: Add qede PMD

Hi Bruce, > From: Richardson, Bruce [mailto:bruce.richardson at intel.com] > Sent: Tuesday, March 22, 2016 4:21 AM > > I've had a quick scan over this patchset, and as you've probably seen I've > made some public comments on it. General comments on the whole > patchset are: > * Please run

[dpdk-dev] [PATCH v2 2/7] drivers/net/e1000: Fix missing brackets

Hi Thomas, Aaron, > > Wenzhuo, do you agree to fix the base driver here? Honestly I find the logic has some problem and maybe more changes needed. I'm talking with our kernel driver contactors to make sure they have no concern about my idea. And Aaron, do we really need to fix this code? For I