From: Jakub Kicinski <kuba@kernel.org>
To: Mina Almasry <almasrymina@google.com>
Cc: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Shuah Khan <shuah@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>,
Bobby Eshleman <bobbyeshleman@meta.com>
Subject: Re: [PATCH net-next v2 1/2] selftests: drv-net: devmem: fix 5-tuple flow steering
Date: Thu, 6 Aug 2026 12:16:31 -0700 [thread overview]
Message-ID: <20260806121631.13175f7e@kernel.org> (raw)
In-Reply-To: <20260803181852.491437-1-almasrymina@google.com>
On Mon, 3 Aug 2026 18:18:25 +0000 Mina Almasry wrote:
> When configuring traffic for the devmem tests, 5-tuple flow steering may
> be required if the environment does not provide network namespaces.
> Pass the correct remote address parameter and fall back to 5-tuple flow
> steering if netns is not available.
Could you clarify what existing upstream test / scenario needs this?
next prev parent reply other threads:[~2026-08-06 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-03 18:18 [PATCH net-next v2 1/2] selftests: drv-net: devmem: fix 5-tuple flow steering Mina Almasry
2026-08-03 18:18 ` [PATCH net-next v2 2/2] selftests: drv-net: ncdevmem: gracefully retry bind() Mina Almasry
2026-08-06 19:16 ` Jakub Kicinski
2026-08-06 19:27 ` Mina Almasry
2026-08-06 19:16 ` Jakub Kicinski [this message]
2026-08-06 20:05 ` [PATCH net-next v2 1/2] selftests: drv-net: devmem: fix 5-tuple flow steering Mina Almasry
2026-08-06 20:34 ` Jakub Kicinski
2026-08-06 20:59 ` Mina Almasry
2026-08-07 21:54 ` Jakub Kicinski
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=20260806121631.13175f7e@kernel.org \
--to=kuba@kernel.org \
--cc=almasrymina@google.com \
--cc=andrew+netdev@lunn.ch \
--cc=bobbyeshleman@meta.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=shuah@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.