From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: Re: [PATCH] app/testpmd: add flag to enable RSS for single-queue
Date: Tue, 22 Jul 2025 16:09:45 +0100 [thread overview]
Message-ID: <aH-puUrmc7ILq6Ok@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20250722070815.620df80d@hermes.local>
On Tue, Jul 22, 2025 at 07:08:15AM -0700, Stephen Hemminger wrote:
> On Tue, 15 Jul 2025 12:53:30 +0000
> Bruce Richardson <bruce.richardson@intel.com> wrote:
>
> > For testing purposes it can be desirable to enable RSS even when only a
> > single queue per port is in use. Add an "enable-rss" flag to testpmd to
> > match the existing "disable-rss" flag.
> >
> > Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> > ---
>
> Not sure about this.
> It makes no sense to have RSS enabled with single queue.
> Maybe you want the hash but no steering?
>
Yep, that is one scenario we have seen it being used in the past. Also,
it's a useful "harmless" offload that can be used to check that the offload
paths in the NIC are working correctly.
> But the DPDK RSS flag doesn't require driver to produce HASH.
>
> I would even argue that ethdev layer should warn application
> trying to do single queue and RSS.
I definitely don't think it should warn about it, because there are
definitely usecases where you may want it enabled for single-queue case,
e.g. when using NIC that provides the hash. However, it should not be the
default, which is why this is a separate enabling flag.
Another reason it's good to have it, is to ensure that when testing single
queue vs multi-queue setups, we can test with the exact same configuration
between those two scenarios. Without the ability to enable RSS, then
multi-queue will always have a different NIC configuration to single queue.
In the case of some of our drivers, for example, the lack of any offloads
such as RSS causes a different faster RX path to be chosen in the
single-queue case, since no packet flags need to be handled.
/Bruce
prev parent reply other threads:[~2025-07-22 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 12:53 Bruce Richardson
2025-07-22 14:08 ` Stephen Hemminger
2025-07-22 15:09 ` Bruce Richardson [this message]
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=aH-puUrmc7ILq6Ok@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).