From: Stephen Hemminger <stephen@networkplumber.org>
To: a.schollmeyer@syseleven.de
Cc: Aman Singh <aman.deep.singh@intel.com>, dev@dpdk.org
Subject: Re: [PATCH] app/testpmd: warn on shared rxq switch mismatch
Date: Mon, 23 Mar 2026 09:17:25 -0700 [thread overview]
Message-ID: <20260323091725.3440ad89@phoenix.local> (raw)
In-Reply-To: <20251125102207.428661-1-a.schollmeyer@syseleven.de>
On Tue, 25 Nov 2025 11:22:07 +0100
a.schollmeyer@syseleven.de wrote:
> From: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
>
> Shared Rx queues do not work with every combination of ports. Besides
> requiring the corresponding device capability, shared Rx queues also
> require all ports of one share group and queue ID have the same switch
> domain and Rx domain. When these fields do not match, shared Rx queues
> are not properly set up and queue sharing may fail silently. This can
> happen even in some less intuitive cases like multiple VFs of one
> physical NIC.
>
> To make debugging issues with shared Rx queue configuration easier, this
> commit introduces simple checks and warning messages for all members of
> a share_group and share_qid to warn whenever there is a mismatch in the
> switch and Rx domain.
>
> Signed-off-by: Adrian Schollmeyer <a.schollmeyer@syseleven.de>
> ---
Why is this not handled at ethdev or device level?
Testpmd is just a test program. Real applications might make same mistake.
next prev parent reply other threads:[~2026-03-23 16:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 10:22 [PATCH] app/testpmd: warn on shared rxq switch mismatch a.schollmeyer
2025-11-25 14:30 ` Stephen Hemminger
2025-11-26 10:40 ` [PATCH v2] " a.schollmeyer
2025-11-26 15:02 ` Stephen Hemminger
2025-12-01 10:22 ` [PATCH v3] app/testpmd: fail " a.schollmeyer
2025-12-02 23:53 ` Stephen Hemminger
2026-03-23 13:46 ` Dariusz Sosnowski
2026-03-23 16:17 ` Stephen Hemminger [this message]
2026-03-24 9:04 ` [PATCH] app/testpmd: warn " Dariusz Sosnowski
2026-03-25 13:04 ` Adrian Schollmeyer
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=20260323091725.3440ad89@phoenix.local \
--to=stephen@networkplumber.org \
--cc=a.schollmeyer@syseleven.de \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.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