From: Jakub Kicinski <kuba@kernel.org>
To: Jason Wang <jasowang@redhat.com>
Cc: willemdebruijn.kernel@gmail.com, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
mst@redhat.com, eperezma@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
virtualization@lists.linux.dev,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH V2 net-next 2/2] vhost-net: reduce one userspace copy when building XDP buff
Date: Fri, 27 Jun 2025 17:48:25 -0700 [thread overview]
Message-ID: <20250627174825.667e1e5f@kernel.org> (raw)
In-Reply-To: <20250626021445.49068-2-jasowang@redhat.com>
On Thu, 26 Jun 2025 10:14:45 +0800 Jason Wang wrote:
> --- a/drivers/vhost/net.c
> +++ b/drivers/vhost/net.c
> @@ -690,13 +690,13 @@ static int vhost_net_build_xdp(struct vhost_net_virtqueue *nvq,
> if (unlikely(!buf))
> return -ENOMEM;
>
> - copied = copy_from_iter(buf, sock_hlen, from);
> - if (copied != sock_hlen) {
> + copied = copy_from_iter(buf + pad - sock_hlen, len, from);
> + if (copied != len) {
> ret = -EFAULT;
> goto err;
> }
>
> - gso = buf;
> + gso = buf + pad - sock_hlen;
>
> if (!sock_hlen)
> memset(buf, 0, pad);
> @@ -715,12 +715,8 @@ static int vhost_net_build_xdp(struct vhost_net_virtqueue *nvq,
> }
> }
>
> - len -= sock_hlen;
we used to adjust @len here, now we don't..
> - copied = copy_from_iter(buf + pad, len, from);
> - if (copied != len) {
> - ret = -EFAULT;
> - goto err;
> - }
> + /* pad contains sock_hlen */
> + memcpy(buf, buf + pad - sock_hlen, sock_hlen);
>
> xdp_init_buff(xdp, buflen, NULL);
> xdp_prepare_buff(xdp, buf, pad, len, true);
.. yet we still use len as the packet size here.
--
pw-bot: cr
next prev parent reply other threads:[~2025-06-28 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 2:14 [PATCH V2 net-next 1/2] tun: remove unnecessary tun_xdp_hdr structure Jason Wang
2025-06-26 2:14 ` [PATCH V2 net-next 2/2] vhost-net: reduce one userspace copy when building XDP buff Jason Wang
2025-06-28 0:48 ` Jakub Kicinski [this message]
2025-06-30 3:36 ` Jason 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=20250627174825.667e1e5f@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.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=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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 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.