From: wangyunjian <wangyunjian@huawei.com>
To: Paolo Abeni <pabeni@redhat.com>,
"mst@redhat.com" <mst@redhat.com>,
"willemdebruijn.kernel@gmail.com"
<willemdebruijn.kernel@gmail.com>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"bjorn@kernel.org" <bjorn@kernel.org>,
"magnus.karlsson@intel.com" <magnus.karlsson@intel.com>,
"maciej.fijalkowski@intel.com" <maciej.fijalkowski@intel.com>,
"jonathan.lemon@gmail.com" <jonathan.lemon@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "bpf@vger.kernel.org" <bpf@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>,
xudingke <xudingke@huawei.com>,
"liwei (DT)" <liwei395@huawei.com>
Subject: RE: [PATCH net-next v2 2/3] vhost_net: Call peek_len when using xdp
Date: Thu, 29 Feb 2024 13:17:33 +0000 [thread overview]
Message-ID: <3841008ad79642d694779aaeac87516e@huawei.com> (raw)
In-Reply-To: <94bd28f625f7ca066e8f2b2686c2493cfab386bd.camel@redhat.com>
> -----Original Message-----
> From: Paolo Abeni [mailto:pabeni@redhat.com]
> Sent: Thursday, February 29, 2024 6:49 PM
> To: wangyunjian <wangyunjian@huawei.com>; mst@redhat.com;
> willemdebruijn.kernel@gmail.com; jasowang@redhat.com; kuba@kernel.org;
> bjorn@kernel.org; magnus.karlsson@intel.com; maciej.fijalkowski@intel.com;
> jonathan.lemon@gmail.com; davem@davemloft.net
> Cc: bpf@vger.kernel.org; netdev@vger.kernel.org;
> linux-kernel@vger.kernel.org; kvm@vger.kernel.org;
> virtualization@lists.linux.dev; xudingke <xudingke@huawei.com>; liwei (DT)
> <liwei395@huawei.com>
> Subject: Re: [PATCH net-next v2 2/3] vhost_net: Call peek_len when using xdp
>
> On Wed, 2024-02-28 at 19:05 +0800, Yunjian Wang wrote:
> > If TUN supports AF_XDP TX zero-copy, the XDP program will enqueue
> > packets to the XDP ring and wake up the vhost worker. This requires
> > the vhost worker to call peek_len(), which can be used to consume XDP
> > descriptors.
> >
> > Signed-off-by: Yunjian Wang <wangyunjian@huawei.com>
> > ---
> > drivers/vhost/net.c | 17 ++++++++++++-----
> > 1 file changed, 12 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c index
> > f2ed7167c848..077e74421558 100644
> > --- a/drivers/vhost/net.c
> > +++ b/drivers/vhost/net.c
> > @@ -207,6 +207,11 @@ static int vhost_net_buf_peek_len(void *ptr)
> > return __skb_array_len_with_tag(ptr); }
> >
> > +static bool vhost_sock_xdp(struct socket *sock) {
> > + return sock_flag(sock->sk, SOCK_XDP); }
> > +
> > static int vhost_net_buf_peek(struct vhost_net_virtqueue *nvq) {
> > struct vhost_net_buf *rxq = &nvq->rxq; @@ -214,6 +219,13 @@ static
> > int vhost_net_buf_peek(struct vhost_net_virtqueue *nvq)
> > if (!vhost_net_buf_is_empty(rxq))
> > goto out;
> >
> > + if (ptr_ring_empty(nvq->rx_ring)) {
> > + struct socket *sock = vhost_vq_get_backend(&nvq->vq);
> > + /* Call peek_len to consume XSK descriptors, when using xdp */
> > + if (vhost_sock_xdp(sock) && sock->ops->peek_len)
> > + sock->ops->peek_len(sock);
>
> This really looks like a socket API misuse. Why can't you use ptr-ring primitives
> to consume XSK descriptors? peek_len could be constified some day, this code
> will prevent such (good) thing.
Thank you for your suggestion. I will consider that with Patch 3/3.
>
> Cheers,
>
> Paolo
prev parent reply other threads:[~2024-02-29 13:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 11:05 [PATCH net-next v2 2/3] vhost_net: Call peek_len when using xdp Yunjian Wang
2024-02-29 10:48 ` Paolo Abeni
2024-02-29 13:17 ` wangyunjian [this message]
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=3841008ad79642d694779aaeac87516e@huawei.com \
--to=wangyunjian@huawei.com \
--cc=bjorn@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=jonathan.lemon@gmail.com \
--cc=kuba@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei395@huawei.com \
--cc=maciej.fijalkowski@intel.com \
--cc=magnus.karlsson@intel.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xudingke@huawei.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