[dpdk-dev] mmap() hint address

- From: Burakov, Anatoly [mailto:anatoly.bura...@intel.com] Sent: Monday, June 16, 2014 1:00 AM To: RICHARDSON, BRUCE; Gooch, Stephen; dev at dpdk.org Subject: RE: mmap() hint address Hi Bruce, Stephen, > > Hello, > > > > I have seen a case where a secondary DPDK proces

[dpdk-dev] PCIid 0x0436

Hello, Cave Creek has PCI id of 0x0436 for port0 and 0x0438 for port1. However only 0x0438 is listed in rte_pci_dev_ids.h. Why is 0x0436 not listed? Best Regards - Stephen

[dpdk-dev] PCIid 0x0436

Thanks for the answer off line. 0x0436 is the DID not handled by the OS network driver. I incorrectly read the Cave Creek document. - Stephen From: Gooch, Stephen Sent: Friday, June 20, 2014 3:40 PM To: dev at dpdk.org Subject: PCIid 0x0436 Hello, Cave Creek has PCI id of 0x0436 for port0

[dpdk-dev] mmap() hint address

Hello, I have seen a case where a secondary DPDK process tries to map uio resource in which mmap() normally sends the corresponding virtual address as a hint address. However on some instances mmap() returns a virtual address that is not the hint address, and it result in rte_panic() and the s