[dpdk-dev] [PATCH v1] doc: add template release notes for 17.02

2016-11-14 Thread Remy Horton
On 14/11/2016 20:31, John McNamara wrote: > Add template release notes for DPDK 17.02 with inline > comments and explanations of the various sections. > > Signed-off-by: John McNamara Acked-by: Remy Horton

[dpdk-dev] [PATCH v1 2/2] net/i40e: fix spelling errors

2016-11-14 Thread Kevin Traynor
On 11/14/2016 06:14 AM, Remy Horton wrote: > Fixes: da61cd084976 ("i40evf: add extended stats") > Fixes: 0eedec25ea36 ("i40e: clean log messages") > Acked-by: Kevin Traynor > Signed-off-by: Remy Horton > --- > drivers/net/i40e/i40e_ethdev.c| 2 +- > drivers/net/i40e/i40e_ethdev_vf.c | 6 +

[dpdk-dev] [PATCH v1 1/2] net/i40e: fix incorrect xstats value mapping

2016-11-14 Thread Kevin Traynor
On 11/14/2016 06:14 AM, Remy Horton wrote: > The offsets used in rte_i40evf_stats_strings for transmission > statistics were wrong, returning the total byte count rather than > the respective (unicast, multicast, broadcast, drop, & error) > packet counts. > > Fixes: da61cd084976 ("i40evf: add exte

[dpdk-dev] Clarification for eth_driver changes

2016-11-14 Thread Ferruh Yigit
On 11/12/2016 5:44 PM, Shreyansh Jain wrote: > Hello Ferruh, > > (Please ignore if line wrappings are not correct. Using a possibly > unconfigured mail client). > >> -Original Message- >> From: Ferruh Yigit [mailto:ferruh.yigit at intel.com] >> Sent: Saturday, November 12, 2016 12:46 AM >

[dpdk-dev] XL710 with DELOCK 86256 qsfp+

2016-11-14 Thread Nagaprabhanjan Bellaru
I just upgraded the XL710 cards with "FW 5.0 API 1.5 NVM 05.00.04 eetrack 80002505" firmware which, I believe, is the latest. Thanks, -nagp On Mon, Nov 14, 2016 at 3:49 PM, Nagaprabhanjan Bellaru < nagp.lists at gmail.com> wrote: > Though the ports of XL710 are getting detected by DPDK, when I i

[dpdk-dev] XL710 with DELOCK 86256 qsfp+

2016-11-14 Thread Nagaprabhanjan Bellaru
Though the ports of XL710 are getting detected by DPDK, when I insert the above QSFP twinax cable and try to bring up the port, I get a "Operation not supported" error. When I looked further, I see that trying to bring up the port is resulting in I40E_AQ_RC_EIO and returning I40E_ERR_UNKNOWN_PHY.

[dpdk-dev] Running 2 process on the same machine

2016-11-14 Thread Bruce Richardson
On Tue, Nov 08, 2016 at 02:02:32PM +0200, Keren Hochman wrote: > Also, I can't understand how to define socket-mem. I did not see anything > related to hugepages in /etc/sysctl.conf. Can i mount hugepages to 2 > different dirs instead and use --huge-dir ? > Thank you. > Doing so would be a replace

[dpdk-dev] [PATCH v1] doc: add template release notes for 17.02

2016-11-14 Thread Thomas Monjalon
> > Add template release notes for DPDK 17.02 with inline > > comments and explanations of the various sections. > > > > Signed-off-by: John McNamara > > Acked-by: Remy Horton Applied, thanks We are ready to start a new release cycle. The version in the master branch is now 17.02-rc0.

[dpdk-dev] two different threads polls the same port, different queues, why the throughput is the same

2016-11-14 Thread Kyle Larose
On Mon, Nov 14, 2016 at 2:28 PM, ?? wrote: > Hi all, > > > I have two threads process the packets with different ways. thread A (core 0) > is very heavy, thread B (core 1) is very light. If I just run each of them, > their throughput is huge different with small packet. Thread A polls queue 0

[dpdk-dev] [PATCH v2] doc: add sub-repositories information

2016-11-14 Thread Thomas Monjalon
2016-11-11 13:34, Ferruh Yigit: > DPDK switched to main and sub-repositories approach, this patch > documents new approach and updates development process according. > > Signed-off-by: Ferruh Yigit > Acked-by: John McNamara Applied, thanks

[dpdk-dev] [PATCH] maintainers: add staging tree for network drivers

2016-11-14 Thread Thomas Monjalon
> > Networking Drivers > > -- > > +M: Ferruh Yigit > > +T: git://dpdk.org/next/dpdk-next-net > > Acked-by: Thomas Monjalon > > It will be applied at the beginning of 17.02 cycle to reflect the change. Applied, thanks. So from now, Ferruh will be responsible of the next-net t

[dpdk-dev] two different threads polls the same port, different queues, why the throughput is the same

2016-11-14 Thread 张伟
I do not have any lock/critical sections in my code. I have logs to print out the core id, src port, dst port and queue id. worker 0 runs on core 1, run macswap very light, the throughput is 4.5Mpps. worker 1 runs on core2, is a load balancer heavy, the throughput is also 4.5Mpps. This does

[dpdk-dev] [PATCH v1 2/2] net/i40e: fix spelling errors

2016-11-14 Thread Remy Horton
Fixes: da61cd084976 ("i40evf: add extended stats") Fixes: 0eedec25ea36 ("i40e: clean log messages") Signed-off-by: Remy Horton --- drivers/net/i40e/i40e_ethdev.c| 2 +- drivers/net/i40e/i40e_ethdev_vf.c | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/i4

[dpdk-dev] [PATCH v1 1/2] net/i40e: fix incorrect xstats value mapping

2016-11-14 Thread Remy Horton
The offsets used in rte_i40evf_stats_strings for transmission statistics were wrong, returning the total byte count rather than the respective (unicast, multicast, broadcast, drop, & error) packet counts. Fixes: da61cd084976 ("i40evf: add extended stats") Signed-off-by: Remy Horton --- drivers/

[dpdk-dev] [PATCH v1 0/2] XStats fixes

2016-11-14 Thread Remy Horton
The offsets used in rte_i40evf_stats_strings for transmission statistics were wrong, returning the total byte count rather than the respective (unicast, multicast, broadcast, drop, & error) packet counts. This patchset also fixes some spelling errors. Fixes: da61cd084976 ("i40evf: add extended st

[dpdk-dev] two different threads polls the same port, different queues, why the throughput is the same

2016-11-14 Thread 张伟
Hi all, I have two threads process the packets with different ways. thread A (core 0) is very heavy, thread B (core 1) is very light. If I just run each of them, their throughput is huge different with small packet. Thread A polls queue 0 of port 0, thread B polls queue 1 of port 0. If I ru

[dpdk-dev] [PATCH] vmxnet3: fix Rx deadlock

2016-11-14 Thread Stefan Puiu
Our use case is that we have an app that needs to keep mbufs around for a while. We've seen cases when calling vmxnet3_post_rx_bufs() from vmxet3_recv_pkts(), it might not succeed to add any mbufs to any RX descriptors (where it returns -err). Since there are no mbufs that the virtual hardware can

[dpdk-dev] [PATCH] vmxnet3: fix Rx deadlock

2016-11-14 Thread Stefan Puiu
Our use case is that we have an app that needs to keep mbufs around for a while. We've seen cases when calling vmxnet3_post_rx_bufs() from vmxet3_recv_pkts(), it might not succeed to add any mbufs to any RX descriptors (where it returns -err). Since there are no mbufs that the virtual hardware can

[dpdk-dev] [PATCH v1] doc: add template release notes for 17.02

2016-11-14 Thread John McNamara
Add template release notes for DPDK 17.02 with inline comments and explanations of the various sections. Signed-off-by: John McNamara --- doc/guides/rel_notes/index.rst | 1 + doc/guides/rel_notes/release_17_02.rst | 223 + 2 files changed, 224 insertion

[dpdk-dev] [PATCH] lib/librte_mempool: a redundant word in comment

2016-11-14 Thread Wei Zhao
From: zhao wei There is a redundant repetition word "for" in commnet line the file rte_mempool.h after the definition of RTE_MEMPOOL_OPS_NAMESIZE. The word "for"appear twice in line 359 and 360.One of them is redundant, so delete it. Fixes: 449c49b93a6b ("lib/librte_mempool: mempool: support han

[dpdk-dev] [PATCH] lib/librte_mempool: a redundant word in comment

2016-11-14 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wei Zhao > Sent: Monday, November 14, 2016 2:47 AM > To: dev at dpdk.org > Cc: olivier.matz at 6wind.com; Zhao1, Wei > Subject: [dpdk-dev] [PATCH] lib/librte_mempool: a redundant word in > comment > > From: z

[dpdk-dev] [PATCH] lib/librte_mempool: a redundant of socket_id assignment

2016-11-14 Thread Mcnamara, John
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Wei Zhao > Sent: Monday, November 14, 2016 2:16 AM > To: dev at dpdk.org > Cc: olivier.matz at 6wind.com; Zhao1, Wei > Subject: [dpdk-dev] [PATCH] lib/librte_mempool: a redundant of socket_id > assignment > >

[dpdk-dev] [PATCH] lib/librte_mempool: a redundant of socket_id assignment

2016-11-14 Thread Wei Zhao
From: zhao wei There is a redundant repetition mempool socket_id assignment in the file rte_mempool.c in function rte_mempool_create_empty.The statement "mp->socket_id = socket_id;"appear twice in line 821 and 824.One of them is redundant, so delete it. Fixes: 85226f9c526b ("lib/librte_mempool:

[dpdk-dev] Clarification for eth_driver changes

2016-11-14 Thread David Marchand
On Fri, Nov 11, 2016 at 8:16 PM, Ferruh Yigit wrote: > On 11/10/2016 11:05 AM, Shreyansh Jain wrote: >> On Thursday 10 November 2016 01:46 PM, David Marchand wrote: >>> Do we really need to keep a eth_driver ? >> >> No. As you have rightly mentioned below (as well as in your Jan'16 >> post), it is

[dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler

2016-11-14 Thread Neil Horman
On Mon, Nov 14, 2016 at 02:29:24AM +0530, Jerin Jacob wrote: > On Fri, Nov 11, 2016 at 10:34:39AM +, Hemant Agrawal wrote: > > Hi Neil, > >Pmdinfogen compiles with host compiler. It usages > > rte_byteorder.h of the target platform. > > However, if the host compiler is older th

[dpdk-dev] [PATCH 2/2] net: align ethdev and eal driver names

2016-11-14 Thread David Marchand
Hello Ferruh, On Thu, Nov 10, 2016 at 7:46 PM, Ferruh Yigit wrote: > On 11/10/2016 1:51 PM, David Marchand wrote: >> Some virtual pmds report a different name than the vdev driver name >> registered in eal. >> While it does not hurt, let's try to be consistent. >> >> Signed-off-by: David Marchand

[dpdk-dev] pmdinfogen issues: cross compilation for ARM fails with older host compiler

2016-11-14 Thread Jerin Jacob
On Fri, Nov 11, 2016 at 10:34:39AM +, Hemant Agrawal wrote: > Hi Neil, >Pmdinfogen compiles with host compiler. It usages > rte_byteorder.h of the target platform. > However, if the host compiler is older than 4.8, it will be an issue during > cross compilation for some platfo