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: Fri, 14 Aug 2026 13:39:43 -0700 [thread overview]
Message-ID: <20260814133943.45c411d3@kernel.org> (raw)
In-Reply-To: <CAHS8izPQn6a_eUgeL5otUESTRud1COHXg2SuR5g9qce1xJogvA@mail.gmail.com>
On Fri, 14 Aug 2026 13:24:48 -0700 Mina Almasry wrote:
> > No no, I just meant a trivial test that installs the rule and maybe
> > sends a packet to check via getsockopt(NAPI_ID) that it arrived on
> > the right queue.
> >
> > You can probably extend ntuple.py instead. I was thinking yesterday
> > that it's nice to have all zcrx stuff in one place. But in reality
> > we already have a bunch of scripts testing zcrx so ntuple.py is
> > probably better.
>
> Ack, will do. I assume you mean do that in a separate series. I'll
> submit another series that extends ntuple.py with 2 tests, one for
> 3-tuple and one for 5-tuple flow steering.
Same series, please.
next prev parent reply other threads:[~2026-08-14 20:39 UTC|newest]
Thread overview: 12+ 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 ` [PATCH net-next v2 1/2] selftests: drv-net: devmem: fix 5-tuple flow steering Jakub Kicinski
2026-08-06 20:05 ` Mina Almasry
2026-08-06 20:34 ` Jakub Kicinski
2026-08-06 20:59 ` Mina Almasry
2026-08-07 21:54 ` Jakub Kicinski
2026-08-14 20:24 ` Mina Almasry
2026-08-14 20:39 ` Jakub Kicinski [this message]
2026-08-14 21:17 ` Mina Almasry
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=20260814133943.45c411d3@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.