On Mon, Oct 26, 2026 at 10:47:11AM +0000, Anurag Mandal wrote:
> An RSS flow rule only selects the hash input set of a packet type, and
> the PF keeps a single configuration per packet type for the VF VSI.
> When a second rule is created for a packet type already used by another
> rule, the PF silently replaces the first configuration, while both flow
> handles remain valid.
> For example,:
>
> flow create 0 ingress pattern eth / vlan vid is 1500 / ipv6 / end
> actions rss types ipv6 l3-dst-only end queues end / end
> flow create 0 ingress pattern eth / vlan vid is 2640 / ipv6 / end
> actions rss types ipv6 l3-src-only end queues end / end
>
> Only the second rule is applied, whatever the VLAN ID of the packet, and
> destroying it leaves the first rule without any hardware configuration.
>
> Reject the creation of an RSS rule when another RSS rule of the port
> already uses the same protocol header stack. The existing rule has to
> be destroyed first to change the hash input set of that packet type.
> Raw pattern rules are not checked, as their packet type is only known
> by the PF parser.
>
> Fixes: 7be10c3004be ("net/iavf: add RSS configuration for VF")
> Cc: [email protected]
>
> Signed-off-by: Anurag Mandal <[email protected]>
> ---
> drivers/net/intel/iavf/iavf_hash.c | 47 ++++++++++++++++++++++++++++++
> 1 file changed, 47 insertions(+)
Acked-by: Bruce Richardson <[email protected]>
Patch applied to dpdk-next-net-intel.
/Bruce
