From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org
Cc: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: Understanding Flow API action RSS
Date: Wed, 29 Dec 2021 17:34:18 +0300 (MSK) [thread overview]
Message-ID: <76f98055-c517-5185-b79-d16ec5ef5ff@oktetlabs.ru> (raw)
Hi all,
In 'rte_flow.h', there is 'struct rte_flow_action_rss'. In it, 'queue' is
to provide "Queue indices to use". But it is unclear whether the order of
elements is meaningful or not. Does that matter? Can queue indices repeat?
An ethdev may have "global" RSS setting with an indirection table of some
fixed size (say, 512). In what comes to flow rules, does that size matter?
When the user selects 'RTE_ETH_HASH_FUNCTION_DEFAULT' in action RSS, does
that allow the PMD to configure an arbitrary, non-Toeplitz hash algorithm?
Please advise.
next reply other threads:[~2021-12-29 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 14:34 Ivan Malov [this message]
2022-01-04 12:41 ` Thomas Monjalon
2022-01-04 16:54 ` Stephen Hemminger
2022-01-04 18:29 ` Ivan Malov
2022-01-04 21:56 ` Stephen Hemminger
2022-01-09 12:23 ` Ori Kam
2022-01-09 13:03 ` Ivan Malov
2022-01-10 9:54 ` Ori Kam
2022-01-10 15:04 ` Ivan Malov
2022-01-10 17:18 ` Ori Kam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=76f98055-c517-5185-b79-d16ec5ef5ff@oktetlabs.ru \
--to=ivan.malov@oktetlabs.ru \
--cc=adrien.mazarguil@6wind.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).