I have changed the application to use multiple queues (one rx queue per core and per port). I have also changed the port configuration by making .rxmode.mq_mode = ETH_MQ_RX_RSS and .rx_adv_conf.rss_conf.rss_hf = ETH_RSS_IPV4. Furthermore my modified application works on the development machine but not on the test machine. I was thinking that is a matter of either disabled or not supported feature on that hardware.
Costin -----Original Message----- From: ?? [mailto:[email protected]] Sent: 12 octombrie 2013 04:13 To: Costin Popescu Cc: dev at dpdk.org Subject: Re: [dpdk-dev] Can't make RSS work with 82598EB NIC DPDK1.3.1 or newer obsoletes the l2fwd-vf example. Because l2fwd also works well on virtual function platform. So l2fwd use only one rx queue for each port which attach to one core. Then RSS will not work for only one rx queue. On 2013?10?11? 20:48, Costin Popescu wrote: > Hi everyone! > > I have modified the l2fwd example application provided with dpdk in order to > benefit from RSS. I have a development machine with an Intel I350 NIC (1Gb) > where RSS seem to work (traffic forwarded on all cores). > On the test machine there is a 82598EB based network card and here the RSS > doesn't work, only core 0 is forwarding traffic. > Looking into ixgbe_dev_mq_rx_configure() function from dpdk lib I can see > that for this type of network controller the configuring function exits > immediately. > i.e. if (hw->mac.type == ixgbe_mac_82598EB) return 0; However the > datasheet claims that RSS is supported. > The test machine is an Intel Xeon E5420 @ 2.50GHz. > > Does anyone have an idea about why RSS would not work in the 82598EB case? > > Thanks, > Costin > > --------------------------------------------------------------------------------------------------- Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and may be confidential and/or privileged of Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is not the intended recipient, unauthorized use, forwarding, printing, storing, disclosure or copying is strictly prohibited, and may be unlawful.If you have received this communication in error,please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you. ---------------------------------------------------------------------------------------------------
