From: Azadeh Aftahi <aftahi334@gmail.com>
To: netdev@vger.kernel.org, virtualization@lists.linux.dev,
bpf@vger.kernel.org
Subject: [RFC] virtio-net: AF_XDP zero-copy TX checksum offload
Date: Wed, 7 Oct 2026 17:07:12 -0500 [thread overview]
Message-ID: <247B8E70-8100-419A-95C4-71E43361FF73@gmail.com> (raw)
Hi all,
I'm planning to work on single-buffer AF_XDP zero-copy TX checksum offload for virtio-net.
Current net-next's virtnet_xsk_xmit_one() does not consume XSK TX checksum metadata and uses the shared zeroed virtio header.
I found Xuan's 2021 proposal anticipating separate headers for checksum support, and the merged 2024 zero-copy TX series,
but I couldn't find a checksum-specific follow-up implementation.
The proposed scope is to map the existing XSK checksum metadata API to VIRTIO_NET_F_CSUM,
using a DMA-safe per-packet virtio header whose lifetime extends until TX completion, with corresponding completion, reset, and unbind cleanup.
I would keep the initial scope limited to single-buffer TX: no multi-buffer RX, timestamps, launch time, or GSO.
I'd also add checksum and header-lifetime coverage using the existing XSK selftest framework with QEMU/TAP.
Is anyone already working on this? If not, does this scope and per-packet-header approach sound reasonable for a follow-up patch?
Thanks,
Azadeh
next reply other threads:[~2026-10-07 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 22:07 Azadeh Aftahi [this message]
[not found] <9DB6FE89-98AB-47CF-9B57-5F47FBB6DAE8@gmail.com>
2026-10-08 1:35 ` [RFC] virtio-net: AF_XDP zero-copy TX checksum offload Xuan Zhuo
2026-10-08 20:10 ` Azadeh Aftahi
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=247B8E70-8100-419A-95C4-71E43361FF73@gmail.com \
--to=aftahi334@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux.dev \
/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