[dpdk-dev] how to find transfer rate ?

2013-06-03 Thread Ivan Boule
On 06/01/2013 03:38 PM, Nulik Nol wrote: > Hi all, > I finally bought my Intel NIC (an I340-T2, > E1000_DEV_ID_82580_COPPER_DUAL, dev id 0x150E) and ran the dpdk with > success. But when testing the cards for speed rate with "testpmd" > program provided in the distribution I can't find the Packets

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Damien Millescamps
;, > my_driver_init, > my_driver_id, > - RTE_PCI_DRV_NEED_IGB_UIO, > + 0, > + "igb_uio", > }; > > static int > --- a/lib/librte_pmd_igb/e1000_ethdev.c 2013-05-29 08:45:38.888471864 > -0700 > +++ b/lib/librte_pmd_igb/e1000_eth

[dpdk-dev] [dpdk-announce] DPDK 1.2.3r2 released

2013-06-03 Thread Thomas Monjalon
The new release can be downloaded here: http://dpdk.org/browse/dpdk/tag/?id=v1.2.3r2 Changelog - fixes for: * blacklisting ports sharing a PCI device (e.g. Mellanox ConnectX-3) * log buffer overflow * test-pmd tx-only - enhan

[dpdk-dev] [PATCH 0/7] Vyatta patches

2013-06-03 Thread Thomas Monjalon
30/05/2013 19:12, Stephen Hemminger : > This is a subset of the Vyatta patches we use. They include some bug > fixes and simple changes to make life easier. It would be nice to have these 7 patches in the next release (dpdk-1.2.3r3). Reviewers are welcomed ! -- Thomas

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Stephen Hemminger
On Mon, 03 Jun 2013 10:58:01 +0200 Damien Millescamps wrote: > comments inlined. > > On 05/30/2013 07:12 PM, Stephen Hemminger wrote: > > An additional change is that failure to detect module should not be fatal, > > but an error like other EAL setup problems, allowing the application > > to rec

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Antti Kantee
On 03.06.2013 10:58, Damien Millescamps wrote: >> }; >> >> -/** Device needs igb_uio kernel module */ >> -#define RTE_PCI_DRV_NEED_IGB_UIO 0x0001 >> /** Device driver must be registered several times until failure */ >> -#define RTE_PCI_DRV_MULTIPLE 0x0002 >> +#define RTE_PCI_DRV_MULTIPLE 0x000

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Thomas Monjalon
03/06/2013 18:08, Antti Kantee : > On 03.06.2013 10:58, Damien Millescamps wrote: > >> -/** Device needs igb_uio kernel module */ > >> -#define RTE_PCI_DRV_NEED_IGB_UIO 0x0001 > >> > >> /** Device driver must be registered several times until failure */ > >> > >> -#define RTE_PCI_DRV_MULTIPLE 0

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Thomas Monjalon
03/06/2013 17:41, Stephen Hemminger : > On Mon, 03 Jun 2013 10:58:01 +0200 > Damien Millescamps wrote: > > > > > > --- a/lib/librte_eal/common/include/rte_pci.h 2013-05-29 > > > 08:45:38.0 -0700 +++ > > > b/lib/librte_eal/common/include/rte_pci.h 2013-05-29 > > > 09:02:50.0 -0

[dpdk-dev] [PATCH 5/7] pci: support multiple PCI regions per device

2013-06-03 Thread Thomas Monjalon
Please, could you provide a commit log to better explain your patch ? -- Thomas

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Stephen Hemminger
On Mon, 3 Jun 2013 18:29:02 +0200 Thomas Monjalon wrote: > 03/06/2013 18:08, Antti Kantee : > > On 03.06.2013 10:58, Damien Millescamps wrote: > > >> -/** Device needs igb_uio kernel module */ > > >> -#define RTE_PCI_DRV_NEED_IGB_UIO 0x0001 > > >> > > >> /** Device driver must be registered se

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Stephen Hemminger
On Mon, 3 Jun 2013 18:36:52 +0200 Thomas Monjalon wrote: > 03/06/2013 17:41, Stephen Hemminger : > > On Mon, 03 Jun 2013 10:58:01 +0200 > > Damien Millescamps wrote: > > > > > > > > --- a/lib/librte_eal/common/include/rte_pci.h 2013-05-29 > > > > 08:45:38.0 -0700 +++ > > > > b/lib/lib

[dpdk-dev] [PATCH 4/7] eal: support different modules

2013-06-03 Thread Antti Kantee
On 03.06.2013 18:29, Thomas Monjalon wrote: >> Is breaking the API a bad thing in this context? IMHO the >> initialization APIs need work before they're general enough and >> perpetually supporting the current ones seems like an unnecessary >> burden. I'm trying to understand the general guidelin