From: Jerome Tollet <jtollet@cisco.com>
To: Marcin Knap <marcin.knap@vecima.com>
Cc: netdev@vger.kernel.org,
Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Subject: Re: [PATCH net v3] xsk: Do not free ZC Rx buffer when the Rx ring is full
Date: Wed, 04 Nov 2026 15:27:17 +0100 [thread overview]
Message-ID: <179380243798.98051.18195517640983587855@cisco.com> (raw)
In-Reply-To: <20261104-xsk-zc-rx-double-free-v3-1-11a0c7ef1973@vecima.com>
Hi Marcin,
Since v3 has no code changes from v2, please feel free to add:
Tested-by: Jerome Tollet <jtollet@cisco.com>
My ConnectX-5 test results are in my earlier reply:
https://lists.openwall.net/netdev/2026/10/30/342
With both earlier mlx5e refill fixes present, the unpatched kernel still
showed RX frame ownership errors with striding RQ, with need_wakeup both
enabled and disabled. The same tests passed with your v2 patch applied.
I have retained the standalone libxsk reproducer used for these tests
and can share it if useful.
Thanks,
Jerome
next prev parent reply other threads:[~2026-11-04 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 8:11 [PATCH net v3] xsk: Do not free ZC Rx buffer when the Rx ring is full Marcin Knap via B4 Relay
2026-11-04 14:27 ` Jerome Tollet [this message]
2026-11-06 11:11 ` netdev-bot+sashiko
2026-11-06 12:33 ` Marcin Knap
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=179380243798.98051.18195517640983587855@cisco.com \
--to=jtollet@cisco.com \
--cc=maciej.fijalkowski@intel.com \
--cc=marcin.knap@vecima.com \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox