[dpdk-dev] TCP/IP stack - options

2013-09-17 Thread Wiles, Roger Keith
Hi Sujith, Wind River also has a fully integrated TCP/IP stack with network acceleration using DPKD with INP/AAE product. A few have ported lwIP to DPDK, but these stacks are not fully integrated into the whole system meaning the Linux host (at least I do not know of anyone that does). Wind Ri

[dpdk-dev] [dpdk-announce] DPDK 1.4.1r1 released

2013-09-17 Thread Thomas Monjalon
The new release can be downloaded here: http://dpdk.org/browse/dpdk/tag/?id=v1.4.1r1 Since 1.3 releases, the most important changes are: - PCIe multi-BAR - PF support - QoS improvements - RSS RETA configuration - sched library - meter library

[dpdk-dev] [PATCH v2 2/2] pci: use igb_uio mapping only when needed

2013-09-17 Thread Damien Millescamps
On 09/17/2013 12:21 PM, Thomas Monjalon wrote: > pci_uio_map_resource() should only be called for Intel devices > (using igb_uio kernel module). > The flag RTE_PCI_DRV_NEED_IGB_UIO is set for all those devices, even when > RTE_EAL_UNBIND_PORTS is disabled. > > Signed-off-by: Thomas Monjalon Acked-

[dpdk-dev] [PATCH v2 1/2] pci: do not check BAR0 mapping

2013-09-17 Thread Damien Millescamps
On 09/17/2013 12:21 PM, Thomas Monjalon wrote: > From: David Marchand > > Since DPDK 1.4, bars mapping is checked and prevent from initializing > drivers which do not use igb_uio mapping. > There is no need to check for bars mapping, especially BAR0 is not required. > If bars mapping failed, then

[dpdk-dev] [PATCH v2 2/2] pci: use igb_uio mapping only when needed

2013-09-17 Thread Thomas Monjalon
pci_uio_map_resource() should only be called for Intel devices (using igb_uio kernel module). The flag RTE_PCI_DRV_NEED_IGB_UIO is set for all those devices, even when RTE_EAL_UNBIND_PORTS is disabled. Signed-off-by: Thomas Monjalon --- app/test/test_pci.c |2 -- lib/libr

[dpdk-dev] [PATCH v2 1/2] pci: do not check BAR0 mapping

2013-09-17 Thread Thomas Monjalon
From: David Marchand Since DPDK 1.4, bars mapping is checked and prevent from initializing drivers which do not use igb_uio mapping. There is no need to check for bars mapping, especially BAR0 is not required. If bars mapping failed, then pci_uio_map_resource will fail and we won't reach this che

[dpdk-dev] [PATCH v2 0/2] fix non-Intel devices probing

2013-09-17 Thread Thomas Monjalon
This new version split the patch and improve some comments. These patches will be included in the coming release 1.4.1r1. They are needed to load vmxnet3-usermap and virtio-net-pmd with DPDK 1.4. --- David Marchand (1): pci: do not check BAR0 mapping Thomas Monjalon (1): pci: use igb_uio ma

[dpdk-dev] Re: TCP/IP stack - options

2013-09-17 Thread Gil Hellmann
Hi Sujith, To add to the respond given by Mr. Jardin, Wind River also has commercial grade protocol stack that could be used with DPDK libraries and application, it is part of Wind Rivers' INP (Intelligent Networking Platform). Regards, Gil Hellmann

[dpdk-dev] TCP/IP stack - options

2013-09-17 Thread Sujith Sankar (ssujith)
Hi Vincent, Sincere thanks to you for the email ! This is very helpful. I think I'll go with Rump kernel stack to start with, and might think about the other options later. Regards, -Sujith On 17/09/13 2:01 AM, "Vincent JARDIN" wrote: >Hi Sujith, > >NetBSD/Rump is the only open source TCP/IP