[dpdk-dev] apply commit e30a0178d290a4e83dc01f9c2170d4859339c9cf "kni: support RHEL 7.3" to dpdk-stable?

2016-11-30 Thread Roberts, Lee A.
Does it make sense to apply the commit for "kni: support RHEL 7.3" (http://www.dpdk.org/browse/dpdk/commit/lib/librte_eal/linuxapp/kni/ethtool/igb/kcompat.h?id=e30a0178d290a4e83dc01f9c2170d4859339c9cf) to the stable tree to enable clean compilation on RHEL 7.3?

[dpdk-dev] DPDK 2.1 on CentOS 7

2016-01-08 Thread Roberts, Lee A.
The patch has been included in DPDK 2.2.0: http://www.dpdk.org/browse/dpdk/commit/?id=261f0390841d1531d1d0fe88e2375e254cb63716 - Lee Roberts -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Sundar Ramakrishnan Sent: Friday,

[dpdk-dev] dpdk 2.1 building failure on rhel 7.2 rc1

2015-12-03 Thread Roberts, Lee A.
When compiling DPDK 2.1.0 on RHEL 7.2, errors are encountered in ../librte_eal/linuxapp/kni/ethtool/igb/igb_main.c. The following changes can be applied relative to dpdk-2.2.0-rc2 to resolve these issues. - Lee Roberts [root at dp91 lroberts]# diff

[dpdk-dev] Queries on DPDK working with XL710 intel NIC

2015-03-20 Thread Roberts, Lee A.
Nissim, Recent HP ProLiant servers use RMRRs (see https://www.kernel.org/doc/Documentation/Intel-IOMMU.txt) to communicate management information. Use of these RMRRs conflicts with IOMMU usage. On ProLiant Gen8 servers, you have a couple options: 1) If you are doing bare-metal testing and

[dpdk-dev] issue with ixgbevf speed/duplex introduced with commit 8ef32003772a14c61c70b540e41c259c482c2fb6

2014-11-07 Thread Roberts, Lee A.
Thomas, I'm seeing an issue with ixgbevf speed/duplex reporting that appears to have been introduced with commit 8ef32003772a14c61c70b540e41c259c482c2fb6 (http://www.dpdk.org/browse/dpdk/commit/lib/librte_pmd_ixgbe/ixgbe/ixgbe_vf.c?id=8ef32003772a14c61c70b540e41c259c482c2fb6) The issue I'm

[dpdk-dev] testpmd link status reporting for ixgbevf_pmd

2014-10-30 Thread Roberts, Lee A.
Hello, I am running "testpmd" in DPDK 1.7.1, using two ixgbevf devices in my host OS. I am finding that "testpmd" reports link status with speed 100 Mbps and half-duplex: # $RTE_SDK/$RTE_TARGET/app/testpmd -c f -n 4 -- -i ... EAL: PCI device :03:10.2 on NUMA socket 0 EAL: probe driver: