From: Rongzheng Wang <testwrzwrz@gmail.com>
To: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
Cc: Magnus Karlsson <magnus.karlsson@intel.com>,
Jason Xing <kerneljasonxing@gmail.com>,
Stanislav Fomichev <sdf@google.com>,
Jesper Dangaard Brouer <hawk@kernel.org>,
stable@vger.kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 2/2] selftests/bpf: cover AF_XDP multi-buffer TX software checksum
Date: Wed, 28 Oct 2026 23:55:44 +0800 [thread overview]
Message-ID: <20261028155544.12908-1-testwrzwrz@gmail.com> (raw)
In-Reply-To: <auH2yISa8xouAx/3@boxer>
Hi Maciej,
Thanks for the review and for the Reviewed-by on 1/2.
> nit: breaking RCT - I know it's test but Stan payed attention to keeping
> the order...
Fixed in v4. The declaration block now follows the width order used in this
file:
struct xsk_tx_metadata *meta;
struct xdp_desc *tx_desc;
struct udphdr *udph;
struct ethhdr *eth;
struct iphdr *iph;
u16 first_len;
u16 pkt_len;
u8 pkt[256];
u32 offset;
void *data;
__u32 idx;
u32 addr;
int ret;
u32 i;
> would it be worth exercising this up to MAX_SKB_FRAGS ?
> then instead of having this flat layout you would loop over the desc
> count.
Good point. I changed it to loop over the descriptor count and exercise 1,
2, and MAX_SKB_FRAGS + 1 (18) frames. The extra frame is the linear head;
the remaining MAX_SKB_FRAGS frames are skb frags, matching the copy-mode
limit documented in af_xdp.rst. The last descriptor takes the remaining
length so the fragments cannot overrun pkt_len. The updated selftest passes.
I'll send v4 as a new thread.
Thanks,
Rongzheng
next prev parent reply other threads:[~2026-10-28 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 2:50 [PATCH net v3 0/2] xsk: fix multi-buffer TX software checksum Rongzheng Wang
2026-10-28 2:50 ` [PATCH net v3 1/2] xsk: defer software checksum until the skb is complete Rongzheng Wang
2026-10-28 13:21 ` Maciej Fijalkowski
2026-10-28 15:55 ` Rongzheng Wang [this message]
2026-10-28 15:57 ` Stanislav Fomichev
2026-10-30 2:30 ` Jason Xing
2026-10-28 2:50 ` [PATCH net v3 2/2] selftests/bpf: cover AF_XDP multi-buffer TX software checksum Rongzheng Wang
2026-10-28 13:20 ` Maciej Fijalkowski
2026-10-28 16:38 ` Rongzheng Wang
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=20261028155544.12908-1-testwrzwrz@gmail.com \
--to=testwrzwrz@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=hawk@kernel.org \
--cc=kerneljasonxing@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=stable@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 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.