The use of 5-tuple of the source address, destination address, source port, destination port, and the transport protocol type may not be possible due to IP fragmentation, encryption, or inability to parse past IPv6 extensions headers.
Flow label values can be chosen such that they can be used as part of the input to a hash function used in a load distribution scheme. On supporting hardware, the 20-bit Flow Label field in the IPv6 header can be used to perform RSS in the ingress path. Please apply. Example to configure IPv6 flow label based RSS: flow create 0 ingress pattern eth / ipv6 / tcp / end actions rss types ipv6-flow-label end / end Ajit Khaparde (3): ethdev: add support for RSS based on IPv6 flow label app/testpmd: add IPv6 flow label to RSS types net/bnxt: add IPv6 flow label based RSS support app/test-pmd/config.c | 1 + drivers/net/bnxt/bnxt.h | 1 + drivers/net/bnxt/bnxt_ethdev.c | 2 ++ drivers/net/bnxt/bnxt_hwrm.c | 7 +++++++ drivers/net/bnxt/bnxt_vnic.c | 9 +++++++-- lib/ethdev/rte_ethdev.h | 1 + 6 files changed, 19 insertions(+), 2 deletions(-) -- 2.39.2 (Apple Git-143)
smime.p7s
Description: S/MIME Cryptographic Signature
