From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Azadeh Aftahi <aftahi334@gmail.com>
Cc: magnus.karlsson@intel.com, maciej.fijalkowski@intel.com,
sdf@fomichev.me, netdev@vger.kernel.org,
virtualization@lists.linux.dev, bpf@vger.kernel.org,
mst@redhat.com, jasowangio@gmail.com, eperezma@redhat.com
Subject: Re: [RFC] virtio-net: AF_XDP zero-copy TX checksum offload
Date: Thu, 8 Oct 2026 09:35:35 +0800 [thread overview]
Message-ID: <1791423335.8486545-2-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <9DB6FE89-98AB-47CF-9B57-5F47FBB6DAE8@gmail.com>
On Mon, 5 Oct 2026 17:28:35 -0500, Azadeh Aftahi <aftahi334@gmail.com> wrote:
> 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?
It seems no one has taken this work forward yet; I would welcome it if you were
to do so.
Thanks.
>
> Thanks,
> Azadeh
next parent reply other threads:[~2026-10-08 1:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9DB6FE89-98AB-47CF-9B57-5F47FBB6DAE8@gmail.com>
2026-10-08 1:35 ` Xuan Zhuo [this message]
2026-10-08 20:10 ` [RFC] virtio-net: AF_XDP zero-copy TX checksum offload Azadeh Aftahi
2026-10-07 22:07 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=1791423335.8486545-2-xuanzhuo@linux.alibaba.com \
--to=xuanzhuo@linux.alibaba.com \
--cc=aftahi334@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=eperezma@redhat.com \
--cc=jasowangio@gmail.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=sdf@fomichev.me \
--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