From: Bui Quang Minh <minhquangbui99@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>, netdev@vger.kernel.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eugenio Pérez" <eperezma@redhat.com>,
"Andrew Lunn" <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Jesper Dangaard Brouer" <hawk@kernel.org>,
"John Fastabend" <john.fastabend@gmail.com>,
virtualization@lists.linux.dev, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org
Subject: Re: [PATCH net v2 2/2] virtio-net: xsk: rx: move the xdp->data adjustment to buf_to_xdp()
Date: Tue, 24 Jun 2025 21:58:47 +0700 [thread overview]
Message-ID: <ffb4b02e-fadb-4697-b001-7d879ca3b6de@gmail.com> (raw)
In-Reply-To: <e6654755-3aa1-4f4b-a6ab-c7568d8a5d4e@redhat.com>
On 6/24/25 17:17, Paolo Abeni wrote:
> On 6/21/25 4:49 PM, Bui Quang Minh wrote:
>> This commit does not do any functional changes. It moves xdp->data
>> adjustment for buffer other than first buffer to buf_to_xdp() helper so
>> that the xdp_buff adjustment does not scatter over different functions.
>>
>> Signed-off-by: Bui Quang Minh <minhquangbui99@gmail.com>
>> ---
>> drivers/net/virtio_net.c | 16 ++++++++++++++--
>> 1 file changed, 14 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 1eb237cd5d0b..4e942ea1bfa3 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -1159,7 +1159,19 @@ static struct xdp_buff *buf_to_xdp(struct virtnet_info *vi,
>> return NULL;
>> }
>>
>> - xsk_buff_set_size(xdp, len);
>> + if (first_buf) {
>> + xsk_buff_set_size(xdp, len);
>> + } else {
>> + /* This is the same as xsk_buff_set_size but with the adjusted
>> + * xdp->data.
>> + */
>> + xdp->data = xdp->data_hard_start + XDP_PACKET_HEADROOM;
>> + xdp->data -= vi->hdr_len;
>> + xdp->data_meta = xdp->data;
>> + xdp->data_end = xdp->data + len;
>> + xdp->flags = 0;
>> + }
>> +
>> xsk_buff_dma_sync_for_cpu(xdp);
>>
>> return xdp;
>> @@ -1284,7 +1296,7 @@ static int xsk_append_merge_buffer(struct virtnet_info *vi,
>> goto err;
>> }
>>
>> - memcpy(buf, xdp->data - vi->hdr_len, len);
>> + memcpy(buf, xdp->data, len);
>>
>> xsk_buff_free(xdp);
>>
> I'm unsure if this change is in the right direction because it almost
> open-code the existing xsk_buff_set_size() helper - any changes there
> should be reflected here, too.
>
> Also AFAICS xdp->data will now carry a different value, and I guess such
> change is user-visible from the attached xdp program. The commit message
> should at least mentions such fact.
The else path in buf_to_xdp is only triggered when it's called in
xsk_append_merge_buffer. That's also the reason of the memcpy line
change in xsk_append_merge_buffer. xsk_append_merge_buffer will allocate
frag and copy xdp_buff's data to that frag. Previously, after
buf_to_xdp, the xdp->data does not point to correct place yet so when
memcpy, we need to copy from xdp->data - vi->hdr_len. With this change,
we will adjust xdp->data = xdp->data - vi->hdr_len right in buf_to_xdp
and also adjust other fields (xdp->data_end) to the correct place too.
So I don't think there is a functional change in this commit.
Thanks,
Quang Minh.
next prev parent reply other threads:[~2025-06-24 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-21 14:49 [PATCH net v2 0/2] virtio-net: xsk: rx: fix the frame's length check Bui Quang Minh
2025-06-21 14:49 ` [PATCH net v2 1/2] " Bui Quang Minh
2025-06-24 8:25 ` Xuan Zhuo
2025-06-24 10:02 ` Paolo Abeni
2025-06-24 14:36 ` Bui Quang Minh
2025-06-21 14:49 ` [PATCH net v2 2/2] virtio-net: xsk: rx: move the xdp->data adjustment to buf_to_xdp() Bui Quang Minh
2025-06-24 8:26 ` Xuan Zhuo
2025-06-24 8:27 ` Xuan Zhuo
2025-06-24 10:17 ` Paolo Abeni
2025-06-24 14:58 ` Bui Quang Minh [this message]
2025-06-29 5:31 ` Bui Quang Minh
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=ffb4b02e-fadb-4697-b001-7d879ca3b6de@gmail.com \
--to=minhquangbui99@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=hawk@kernel.org \
--cc=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox