Adding Ciara to the thread. Ian
From: Darrell Ball [mailto:[email protected]] Sent: Wednesday, July 12, 2017 10:55 PM To: [email protected] Cc: Kavanagh, Mark B <[email protected]>; Stokes, Ian <[email protected]>; Kevin Traynor <[email protected]>; O Mahony, Billy <[email protected]>; Chandran, Sugesh <[email protected]>; Bodireddy, Bhanuprakash <[email protected]> Subject: RTE RSS configuration Hi OVS-DPDK uses a RTE RSS hash configuration of ETH_RSS_IP | ETH_RSS_UDP | ETH_RSS_TCP I want to get an idea of expected guarantees of bounds of behavior if any. I am trying to understand the lower bound of fields that could go into the RSS hash. For example, could the RSS hash just be based on L3 (ipv4 or ipv6) as best effort and the RSS valid flag be still set to true ? Or, is it guaranteed that if L4 fields are not supported that the RSS valid flag will be false ? On the flip side could we be getting something else included as well like L2 fields (DA and SA, for example) implicitly ?
