[dpdk-dev] PCI device mapping to socket

Hi, It depends on the kernel version. For the latests ones you can use: cat /sys/class/net//device/numa_node in all other case, you can use lspci fallback (in case even no driver is yet loaded). lspci | grep Ethernet 09:00.2 Ethernet controller: Intel Corporation I350 Gigabit Network Connection

[dpdk-dev] PCI device mapping to socket

All, Does anyone know of a way I can find out which socket a PCI device/bridge is tied up to? I have looked into dmidecode and lspci to no avail, but I may be missing something. We are looking at putting multiple NICs into a single dual socket server. This is so that I can tie specific NIC po

[dpdk-dev] regarding this NIC

Should work since the differences are mainly the interfaces. Two versions are available: * 82599EB - PCI Express* (PCIe*) 2.0, dual port 10 Gigabit Ethernet controller for XAUI, KX, KX4, BX, BX4 and CX4 interfaces. * 82599ES - Serial 10 GbE backplane interface for blade implementations (includes

[dpdk-dev] regarding this NIC

Intel(r) 10GbE network controller 82599ES From: Prashant Upadhyaya Sent: Wednesday, December 18, 2013 4:38 PM To: dev at dpdk.org Subject: regarding this NIC Hi, Could somebody advise if this NIC would work with DPDK. It mentions 82599ES, so far I have been working with 82599EB. Regards -Prash

[dpdk-dev] regarding this NIC

Hi, Could somebody advise if this NIC would work with DPDK. It mentions 82599ES, so far I have been working with 82599EB. Regards -Prashant === Please refer to http://www.aricent.com/legal/email_disclaimer.html for

[dpdk-dev] When are mbufs released back to the mempool?

Hello Ken, On 12/17/2013 07:13 PM, Schumm, Ken wrote: > When running l2fwd the number of available mbufs returned by > rte_mempool_count() starts at 7680 on an idle system. > > As traffic commences the count declines from 7680 to > 5632 (expected). You are right, some mbufs are kept at 2 pla