Re: [dpdk-users] DPDK 20.11 - i40e 2 tuple RSS configuration

["Xing, Beilei" <beilei.xing@intel.com>]

Hi,

I remember there's no legacy API rte_eth_dev_filter_ctrl()  supported in 20.11.
Please refer to RSS Flow part in i40e.rst:

Enable hash and set input set for ipv4-tcp.
    testpmd> flow create 0 ingress pattern eth / ipv4 / tcp / end \
      actions rss types ipv4-tcp l3-src-only end queues end / end

BR,
Beilei

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Vishal Mohan
> Sent: Thursday, May 27, 2021 3:40 PM
> To: users@dpdk.org
> Subject: [dpdk-users] DPDK 20.11 - i40e 2 tuple RSS configuration
> 
> I'm trying to implement RSS with 2 tuple (src ip, dst ip) hashing with X710 -
> quad port in DPDK 20.11 with no success. I was able to implement the same
> in DPDK 17.11 with a combination of RSS flags  given below and
> rte_eth_dev_filter_ctrl():
> 
> .rss_hf = (ETH_RSS_IPV4 | ETH_RSS_NONFRAG_IPV4_OTHER |
> ETH_RSS_FRAG_IPV4 | ETH_RSS_NONFRAG_IPV4_UDP |
> ETH_RSS_NONFRAG_IPV4_TCP)
> 
> and selecting input fields as dst and src ip for every rss_hf flag using
> rte_eth_dev_filter_ctrl().
> 
> In DPDK 20.11, I believe there is no explicit usage of using
> rte_eth_dev_filter_ctrl() instead we can configure the hashing with the
> generic rte_flow api. I did configure a flow validate and create the same, but
> the hashing is not working as expected. Without flags
> ETH_RSS_NONFRAG_IPV4_UDP | ETH_RSS_NONFRAG_IPV4_TCP no hashing
> takes place and with those flags included in .rss_hf, 5 tuple hashing takes
> place.
> 
> When using rte_flow api, any flags given in rte_flow_action_rss.types has no
> effect on the final RSS hash result. Also the RSS hashing in the given testpmd
> isn't working when it is configured in "ip" (2 tuple) mode.
> 
> Any inputs for configuring RSS hashing for 2 tuple is much appreciated.
> 
> 
> Thanks & Regards,
>  Vishal Mohan