All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Gal Pressman <gal@nvidia.com>
Cc: Nimrod Oren <noren@nvidia.com>,
	Mohsin Bashir <mohsin.bashr@gmail.com>,
	netdev@vger.kernel.org, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
	shuah@kernel.org, horms@kernel.org, cratiu@nvidia.com,
	cjubran@nvidia.com, mbloch@nvidia.com, jdamato@fastly.com,
	sdf@fomichev.me, ast@kernel.org, daniel@iogearbox.net,
	hawk@kernel.org, john.fastabend@gmail.com, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, bpf@vger.kernel.org,
	linux-kselftest@vger.kernel.org, llvm@lists.linux.dev,
	tariqt@nvidia.com, thoiland@redhat.com
Subject: Re: [PATCH net-next V6 2/5] selftests: drv-net: Test XDP_PASS/DROP support
Date: Mon, 21 Jul 2025 13:33:25 -0700	[thread overview]
Message-ID: <20250721133325.73e2f076@kernel.org> (raw)
In-Reply-To: <eaca90db-897c-45a0-8eed-92c36dbec825@nvidia.com>

IOn Mon, 21 Jul 2025 21:34:05 +0300 Gal Pressman wrote:
> > That's a reasonable way to modify the test. But I'm not sure it's
> > something that should be blocking merging the patches.
> > Or for that matter whether it's Mohsin's responsibility to make the
> > test cater to quirks of mlx5,   
> 
> Definitely not a quirk, you cannot assume the headers are in the linear
> part, especially if you're going to put this program as reference in the
> kernel tree.
> 
> This issue has nothing to do with mlx5, but a buggy XDP program.

We put the tests in the tree to foster collaboration. If you think the
test should be improved please send patches. I don't think the kernel
will allow pulling headers if they are not in the linear section.
But that's your problem to solve.

> > which is not even part of NIPA testing -
> > we have no way of knowing what passes for mlx5, what regresses it etc.  
> 
> People have been developing XDP code that runs on mlx5 long before NIPA
> even existed 🤷‍♂️..
> And as you know we run these selftests on mlx5 hardware, as evident by
> Nimrod's mail, and others you've seen on the list. You know what regresses.

No, please don't try to dispute facts. It's not integrated, if you go
on a vacation upstream will have no idea what broke in mlx5. Either you
are reporting the results upstream or our guarantees on regressions are
best effort. BTW I don't understand how you can claim that a new test
regresses something. It never passed on mlx5 == not a regression.

  reply	other threads:[~2025-07-21 20:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-19  8:30 [PATCH net-next V6 0/5] selftests: drv-net: Test XDP native support Mohsin Bashir
2025-07-19  8:30 ` [PATCH net-next V6 1/5] net: netdevsim: hook in XDP handling Mohsin Bashir
2025-07-19  8:30 ` [PATCH net-next V6 2/5] selftests: drv-net: Test XDP_PASS/DROP support Mohsin Bashir
2025-07-21 11:43   ` Nimrod Oren
2025-07-21 15:40     ` Jakub Kicinski
2025-07-21 18:34       ` Gal Pressman
2025-07-21 20:33         ` Jakub Kicinski [this message]
2025-07-22  7:21           ` Gal Pressman
2025-07-22 13:49             ` Jakub Kicinski
2025-07-22 15:03         ` Paolo Abeni
2025-07-23  6:17           ` Gal Pressman
2025-07-21 19:43     ` Martin KaFai Lau
2025-07-21 20:24       ` Jakub Kicinski
2025-07-19  8:30 ` [PATCH net-next V6 3/5] selftests: drv-net: Test XDP_TX support Mohsin Bashir
2025-07-19  8:30 ` [PATCH net-next V6 4/5] selftests: drv-net: Test tail-adjustment support Mohsin Bashir
2025-07-19  8:30 ` [PATCH net-next V6 5/5] selftests: drv-net: Test head-adjustment support Mohsin Bashir
2025-07-23  1:30 ` [PATCH net-next V6 0/5] selftests: drv-net: Test XDP native support patchwork-bot+netdevbpf
2025-07-23  7:11   ` Gal Pressman
2025-07-23 14:12     ` Jakub Kicinski
2025-07-23 16:01       ` Gal Pressman
2025-07-24  9:05         ` Simon Horman

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=20250721133325.73e2f076@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=cjubran@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=hawk@kernel.org \
    --cc=horms@kernel.org \
    --cc=jdamato@fastly.com \
    --cc=john.fastabend@gmail.com \
    --cc=justinstitt@google.com \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=mbloch@nvidia.com \
    --cc=mohsin.bashr@gmail.com \
    --cc=morbo@google.com \
    --cc=nathan@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=noren@nvidia.com \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=tariqt@nvidia.com \
    --cc=thoiland@redhat.com \
    /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.