[dpdk-dev] [RFC] librte_pmd_null: Add null PMD

From: Tetsuya Mukawa 'null PMD' is a virtual device driver particulary designed to measure performance of DPDK applications and DPDK PMDs. When an application call rx, null PMD just allocate mbufs and return those. Also tx, the PMD just free mbufs. The PMD has following

[dpdk-dev] [RFC] PMD for performance measurement

From: Tetsuya Mukawa Hi, I want to measure throughputs like following cases. - path connected by RING PMDs - path connected by librte_vhost and virtio-net PMD - path connected by MEMNIC PMDs - . Is there anyone want to do same thing? Anyway, I guess those throughputs

[dpdk-dev] rx_eth_tx_burst not work in slave app.

Hi all. I wrote a program to recv and send pkt at the same port. First init the port then use below code to receive pkts and send pkts. It works OK. Then I try the multi-process. I init the port in master app, and run the recv and send in slave spp. In this mode rx_eth_tx_burst() always

[dpdk-dev] Porting DPDK to ARM platform

Hi, Did someone tried porting DPDK to ARM platform? If so please provide some guidance with respect to the changes required. Regards, Mukesh

[dpdk-dev] [PATCH 0/4] Add DSO symbol versioning to support backwards compatibility

On Fri, Sep 19, 2014 at 07:18:36AM -0700, Venkatesan, Venky wrote: > On 9/18/2014 12:14 PM, Neil Horman wrote: > >On Thu, Sep 18, 2014 at 08:23:36PM +0200, Thomas Monjalon wrote: > >>Hi Neil, > >> > >>2014-09-15 15:23, Neil Horman: > >>>The DPDK ABI develops and changes quickly, which makes it

[dpdk-dev] [PATCH 2/2] bond: add mode 4 support

On Fri, Sep 19, 2014 at 12:47:35PM +, Wodkowski, PawelX wrote: > > -Original Message- > > From: Neil Horman [mailto:nhorman at tuxdriver.com] > > Sent: Thursday, September 18, 2014 18:03 > > To: Wodkowski, PawelX > > Cc: dev at dpdk.org; Jastrzebski, MichalX K; Doherty, Declan > >

[dpdk-dev] [PATCH 2/2] bond: add mode 4 support

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Thursday, September 18, 2014 18:03 > To: Wodkowski, PawelX > Cc: dev at dpdk.org; Jastrzebski, MichalX K; Doherty, Declan > Subject: Re: [dpdk-dev] [PATCH 2/2] bond: add mode 4 support > > On Thu, Sep 18,

[dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32

On Fri, Sep 19, 2014 at 10:28:31AM +, Richardson, Bruce wrote: > > > > -Original Message- > > From: Neil Horman [mailto:nhorman at tuxdriver.com] > > Sent: Friday, September 19, 2014 11:25 AM > > To: Richardson, Bruce > > Cc: Thomas Monjalon; dev at dpdk.org > > Subject: Re:

[dpdk-dev] [PATCH 2/4] Provide initial versioning for all DPDK libraries

On Mon, Sep 15, 2014 at 03:23:49PM -0400, Neil Horman wrote: > Add linker version script files to each DPDK library to put a stake in the > ground from which we can start cleaning up API's > > Signed-off-by: Neil Horman > CC: Thomas Monjalon > CC: "Richardson, Bruce" > --- > <... snip for

[dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Friday, September 19, 2014 11:25 AM > To: Richardson, Bruce > Cc: Thomas Monjalon; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32 > > On Fri, Sep 19, 2014 at

[dpdk-dev] [PATCH v3 00/20] cleanup logs in main PMDs

> Here is a patchset that reworks the log macro in e1000, ixgbe and i40e PMDs. > The idea behind this is to make it easier to debug some init failures and to > be > sure of the datapath selected in these PMDs (rx / tx handlers selection). > > The PMDs changes involve adding more debug messages

[dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Thursday, September 18, 2014 7:09 PM > To: Thomas Monjalon > Cc: Richardson, Bruce; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32 > > On Thu, Sep 18, 2014 at

[dpdk-dev] [PATCH v2 3/3] i40evf: support of RSS in VF

i40e hardware supports RSS in VF, the code changes are to add this support. v2 changes: Updating/querying redirection table has been removed, as it will be in another patches of supporting different redirection table sizes soon later. Signed-off-by: Helin Zhang Reviewed-by: Cunming Liang

[dpdk-dev] [PATCH v2 2/3] i40e: extern two functions and relevant macros

To reuse code, 'i40e_config_hena()' and 'i40e_parse_hena()' and their relevant macros need to be extern, and then can be used for both PF and VF parts. Signed-off-by: Helin Zhang Reviewed-by: Cunming Liang Reviewed-by: Jijiang Liu --- lib/librte_pmd_i40e/i40e_ethdev.c | 4 ++--

[dpdk-dev] [PATCH v2 1/3] ethdev: improvement for constant usage

Forced type conversion is not needed to define a macro with constant. The alternate is to let compiler use the default width, or specify the width with suffix of 'U', 'UL', 'ULL', etc. Signed-off-by: Helin Zhang Reviewed-by: Cunming Liang Reviewed-by: Jijiang Liu ---

[dpdk-dev] [PATCH v2 0/3] add i40e RSS support in VF

As hardware supports RSS in VF, the patches add that support in driver. In addition, minor improvements are added for defining macro with constant. v2 changes: * Remove support of updating/querying redirection table, as it will be implemented in another patches later. * Remove changes in

[dpdk-dev] [PATCH 0/4] Add DSO symbol versioning to support backwards compatibility

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Thursday, September 18, 2014 8:14 PM > To: Thomas Monjalon > Cc: dev at dpdk.org; Richardson, Bruce > Subject: Re: [PATCH 0/4] Add DSO symbol versioning to support backwards > compatibility > > On Thu, Sep

[dpdk-dev] [PATCH 0/4] Add DSO symbol versioning to support backwards compatibility

On 9/18/2014 12:14 PM, Neil Horman wrote: > On Thu, Sep 18, 2014 at 08:23:36PM +0200, Thomas Monjalon wrote: >> Hi Neil, >> >> 2014-09-15 15:23, Neil Horman: >>> The DPDK ABI develops and changes quickly, which makes it difficult for >>> applications to keep up with the latest version of the

[dpdk-dev] [PATCH 3/5] testpmd: Change rxfreet default to 32

On Fri, Sep 19, 2014 at 09:18:26AM +, Richardson, Bruce wrote: > > -Original Message- > > From: Neil Horman [mailto:nhorman at tuxdriver.com] > > Sent: Thursday, September 18, 2014 7:09 PM > > To: Thomas Monjalon > > Cc: Richardson, Bruce; dev at dpdk.org > > Subject: Re: [dpdk-dev]

[dpdk-dev] [PATCH 2/4] Provide initial versioning for all DPDK libraries

On Fri, Sep 19, 2014 at 10:45:38AM +0100, Bruce Richardson wrote: > On Mon, Sep 15, 2014 at 03:23:49PM -0400, Neil Horman wrote: > > Add linker version script files to each DPDK library to put a stake in the > > ground from which we can start cleaning up API's > > > > Signed-off-by: Neil Horman

[dpdk-dev] DPDK and custom memory

On Fri, Sep 19, 2014 at 12:13:55AM +, Saygin, Artur wrote: > FWIW: rte_mempool_xmem_create turned out to be exactly what the use case > requires. It's not without limitations but is probably better than having to > copy buffers between device and DPDK memory. > Ah, so its not non-kernel

[dpdk-dev] i40e: Steps and required configurations of how to achieve the best performance!

Hi David I agree with you that we need to re-think of these two configurations. Thank you very much for the good comments! My idea on it could be, 1. Write a script to use ?setpci? to configure pci configuration. End user can decide which PCI device needs to be changed. 2. Add

[dpdk-dev] Maximum possible throughput with the KNI DPDK Application

Hi Sure, multiple queues can be used in any KNI app, actually current ?KNI example app = l2fwd app + kni support?. So you can do in KNI app of what can be done in l2fwd. But you might need to try if it really works with multiple queues in current example KNI app, as I did not test it as that.

[dpdk-dev] DPDK and custom memory

FWIW: rte_mempool_xmem_create turned out to be exactly what the use case requires. It's not without limitations but is probably better than having to copy buffers between device and DPDK memory. -Original Message- From: Neil Horman [mailto:nhor...@tuxdriver.com] Sent: Wednesday,