Thanks for clarifying that this is a limitation of the card. It would be very helpful to update the driver so that only supported hashing configurations are accepted.
Trevor On Mon, Aug 24, 2015 at 7:36 PM, Rose, Gregory V <gregory.v.r...@intel.com> wrote: > Trevor, > > > > The X710 and XL710 devices do not work the same as the NICs supported by > the ixgbe driver so the configuration you’re attempting with the i40e > driver does not work as you would expect on the devices supported by > ixgbe. Intel has received requests from other parties requesting support > for the configuration you’re attempting and the request is under > consideration but at this time we can’t make any commitment as to when that > sort of support might be available. > > > > Regards, > > > > - Greg > > > > *From:* Trevor Highland [mailto:trevor.highl...@gmail.com] > *Sent:* Monday, August 24, 2015 4:51 PM > *To:* Rose, Gregory V > *Cc:* e1000-devel@lists.sourceforge.net > *Subject:* Re: [E1000-devel] i40e RSS configuration > > > > I am running using the 1.3.38 driver. We have also tried using the driver > provided DPDK. I can reproduce this behavior with the following steps. The > traffic we are generating has randomized IP address from several /24 > networks. > > > > root@x:~# lspci | grep 710 > > 82:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 82:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 82:00.2 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 82:00.3 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 83:00.0 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 83:00.1 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 83:00.2 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > 83:00.3 Ethernet controller: Intel Corporation Ethernet 10G 2P X710 > Adapter (rev 01) > > > > root@x:~# modprobe i40e > > root@x:~# ethtool -N p2p4 rx-flow-hash tcp4 sd > > root@x:~# ethtool -N p2p4 rx-flow-hash udp4 sd > > root@x:~# ifconfig p2p4 up > > root@x:~#ethtool -S p2p4 > > NIC statistics: > > rx_packets: 842749216 > > tx_packets: 8 > > rx_bytes: 503124766615 > > tx_bytes: 648 > > rx_errors: 0 > > tx_errors: 0 > > rx_dropped: 0 > > tx_dropped: 0 > > collisions: 0 > > rx_length_errors: 0 > > rx_crc_errors: 0 > > rx_unicast: 842749231 > > tx_unicast: 0 > > rx_multicast: 0 > > tx_multicast: 6 > > rx_broadcast: 0 > > tx_broadcast: 0 > > rx_unknown_protocol: 0 > > fcoe_bad_fccrc: 0 > > rx_fcoe_dropped: 0 > > rx_fcoe_packets: 0 > > rx_fcoe_dwords: 0 > > fcoe_ddp_count: 0 > > fcoe_last_error: 0 > > tx_fcoe_packets: 0 > > tx_fcoe_dwords: 0 > > tx-0.tx_packets: 0 > > tx-0.tx_bytes: 0 > > rx-0.rx_packets: 842749216 > > rx-0.rx_bytes: 503124766615 > > tx-1.tx_packets: 0 > > tx-1.tx_bytes: 0 > > rx-1.rx_packets: 0 > > rx-1.rx_bytes: 0 > > tx-2.tx_packets: 8 > > tx-2.tx_bytes: 648 > > rx-2.rx_packets: 0 > > rx-2.rx_bytes: 0 > > tx-3.tx_packets: 0 > > tx-3.tx_bytes: 0 > > rx-3.rx_packets: 0 > > rx-3.rx_bytes: 0 > > tx-4.tx_packets: 0 > > tx-4.tx_bytes: 0 > > rx-4.rx_packets: 0 > > rx-4.rx_bytes: 0 > > tx-5.tx_packets: 0 > > tx-5.tx_bytes: 0 > > rx-5.rx_packets: 0 > > rx-5.rx_bytes: 0 > > tx-6.tx_packets: 0 > > tx-6.tx_bytes: 0 > > rx-6.rx_packets: 0 > > rx-6.rx_bytes: 0 > > tx-7.tx_packets: 0 > > tx-7.tx_bytes: 0 > > rx-7.rx_packets: 0 > > rx-7.rx_bytes: 0 > > tx-8.tx_packets: 0 > > tx-8.tx_bytes: 0 > > rx-8.rx_packets: 0 > > rx-8.rx_bytes: 0 > > <removed subsequent output> > > > > root@x:~# ethtool -N p2p4 rx-flow-hash tcp4 sdfn > > root@x:~# ethtool -N p2p4 rx-flow-hash udp4 sdfn > > root@x:~# ethtool -S p2p4 > > NIC statistics: > > rx_packets: 995860297 > > tx_packets: 8 > > rx_bytes: 594919177484 > > tx_bytes: 648 > > rx_errors: 0 > > tx_errors: 0 > > rx_dropped: 0 > > tx_dropped: 0 > > collisions: 0 > > rx_length_errors: 0 > > rx_crc_errors: 0 > > rx_unicast: 995860307 > > tx_unicast: 0 > > rx_multicast: 0 > > tx_multicast: 6 > > rx_broadcast: 0 > > tx_broadcast: 0 > > rx_unknown_protocol: 0 > > fcoe_bad_fccrc: 0 > > rx_fcoe_dropped: 0 > > rx_fcoe_packets: 0 > > rx_fcoe_dwords: 0 > > fcoe_ddp_count: 0 > > fcoe_last_error: 0 > > tx_fcoe_packets: 0 > > tx_fcoe_dwords: 0 > > tx-0.tx_packets: 0 > > tx-0.tx_bytes: 0 > > rx-0.rx_packets: 877750096 > > rx-0.rx_bytes: 523937667302 > > tx-1.tx_packets: 0 > > tx-1.tx_bytes: 0 > > rx-1.rx_packets: 1909700 > > rx-1.rx_bytes: 1136954121 > > tx-2.tx_packets: 8 > > tx-2.tx_bytes: 648 > > rx-2.rx_packets: 1895315 > > rx-2.rx_bytes: 1145483514 > > tx-3.tx_packets: 0 > > tx-3.tx_bytes: 0 > > rx-3.rx_packets: 1881385 > > rx-3.rx_bytes: 1152641588 > > tx-4.tx_packets: 0 > > tx-4.tx_bytes: 0 > > rx-4.rx_packets: 1907359 > > rx-4.rx_bytes: 1158220856 > > tx-5.tx_packets: 0 > > tx-5.tx_bytes: 0 > > rx-5.rx_packets: 1855043 > > rx-5.rx_bytes: 1118706052 > > tx-6.tx_packets: 0 > > tx-6.tx_bytes: 0 > > rx-6.rx_packets: 1914796 > > rx-6.rx_bytes: 1134671275 > > tx-7.tx_packets: 0 > > tx-7.tx_bytes: 0 > > rx-7.rx_packets: 1890944 > > rx-7.rx_bytes: 1132133104 > > tx-8.tx_packets: 0 > > tx-8.tx_bytes: 0 > > rx-8.rx_packets: 1892025 > > rx-8.rx_bytes: 1125067639 > > <subsequent output removed> > > > > Thanks, > > Trevor > > > > > > > > > > On Thu, Aug 20, 2015 at 5:28 PM, Rose, Gregory V <gregory.v.r...@intel.com> > wrote: > > How are you configuring the NIC to do this? Are you using a tool or > modifying the source code directly? Also, what driver are you using, what > kernel version? > > - Greg > > > > -----Original Message----- > > From: Trevor Highland [mailto:trevor.highl...@gmail.com] > > Sent: Thursday, August 20, 2015 2:59 PM > > To: e1000-devel@lists.sourceforge.net > > Subject: [E1000-devel] i40e RSS configuration > > > > I am looking to configure an X710 NIC to perform the RSS hashing using > > only the src/dst IP address for all types of IPv4 traffic. When I set the > > RSS configuration to hash on I40E_FILTER_PCTYPE_FRAG_IPV4 and > > I40E_FILTER_PCTYPE_NONF_IPV4_OTHER, non fragmented IPv4 TCP packets are > > always hashed to queue 0. What are the appropriate settings to hash IPv4 > > TCP packets only using the IP addresses as input? It isn't clear from the > > datasheet what the appropriate settings should be, but this configuration > > has been available to ixgbe and igb NICs. > > > > Trevor > > >
------------------------------------------------------------------------------
_______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
