virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Jesper Dangaard Brouer <hawk@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	netdev@vger.kernel.org, John Fastabend <john.fastabend@gmail.com>,
	Eric Dumazet <edumazet@google.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Yunsheng Lin <linyunsheng@huawei.com>,
	Jakub Kicinski <kuba@kernel.org>,
	bpf@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
	virtualization@lists.linux-foundation.org,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next 1/8] virtio_net: mergeable xdp: put old page immediately
Date: Thu, 23 Mar 2023 13:58:09 +0800	[thread overview]
Message-ID: <1679551089.625654-2-xuanzhuo@linux.alibaba.com> (raw)
In-Reply-To: <CACGkMEvS7N1tXFD2-2n2upY15JF6=0uaAebewsP8=K+Cwbtgsg@mail.gmail.com>

On Thu, 23 Mar 2023 13:38:30 +0800, Jason Wang <jasowang@redhat.com> wrote:
> On Thu, Mar 23, 2023 at 9:43 AM Xuan Zhuo <xuanzhuo@linux.alibaba.com> wrote:
> >
> > On Wed, 22 Mar 2023 16:22:18 +0800, Yunsheng Lin <linyunsheng@huawei.com> wrote:
> > > On 2023/3/22 11:03, Xuan Zhuo wrote:
> > > > In the xdp implementation of virtio-net mergeable, it always checks
> > > > whether two page is used and a page is selected to release. This is
> > > > complicated for the processing of action, and be careful.
> > > >
> > > > In the entire process, we have such principles:
> > > > * If xdp_page is used (PASS, TX, Redirect), then we release the old
> > > >   page.
> > > > * If it is a drop case, we will release two. The old page obtained from
> > > >   buf is release inside err_xdp, and xdp_page needs be relased by us.
> > > >
> > > > But in fact, when we allocate a new page, we can release the old page
> > > > immediately. Then just one is using, we just need to release the new
> > > > page for drop case. On the drop path, err_xdp will release the variable
> > > > "page", so we only need to let "page" point to the new xdp_page in
> > > > advance.
> > > >
> > > > Signed-off-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > > ---
> > > >  drivers/net/virtio_net.c | 15 ++++++---------
> > > >  1 file changed, 6 insertions(+), 9 deletions(-)
> > > >
> > > > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > > > index e2560b6f7980..4d2bf1ce0730 100644
> > > > --- a/drivers/net/virtio_net.c
> > > > +++ b/drivers/net/virtio_net.c
> > > > @@ -1245,6 +1245,9 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                     if (!xdp_page)
> > > >                             goto err_xdp;
> > > >                     offset = VIRTIO_XDP_HEADROOM;
> > > > +
> > > > +                   put_page(page);
> > >
> > > the error handling of xdp_linearize_page() does not seems self contained.
> > > Does it not seem better:
> > > 1. if xdp_linearize_page() succesed, call put_page() for first buffer just
> > >    as put_page() is call for other buffer
> > > 2. or call virtqueue_get_buf() and put_page() for all the buffer of the packet
> > >    so the error handling is not needed outside the virtqueue_get_buf().
> > >
> > > In that case, it seems we can just do below without xdp_page:
> > > page = xdp_linearize_page(rq, num_buf, page, ...);
> >
> >
> > This does look better.
> >
> > In fact, we already have vq reset, we can load XDP based on vq reset.
> > In this way, we can run without xdp_linearize_page.
>
> The goal is to try our best not to drop packets, so I think it's
> better to keep it.


Yes. vq reset may drop some packets.

Thanks.

>
> Thanks
>
> >
> >
> > >
> > >
> > > > +                   page = xdp_page;
> > > >             } else if (unlikely(headroom < virtnet_get_headroom(vi))) {
> > > >                     xdp_room = SKB_DATA_ALIGN(VIRTIO_XDP_HEADROOM +
> > > >                                               sizeof(struct skb_shared_info));
> > > > @@ -1259,6 +1262,9 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                            page_address(page) + offset, len);
> > > >                     frame_sz = PAGE_SIZE;
> > > >                     offset = VIRTIO_XDP_HEADROOM;
> > > > +
> > > > +                   put_page(page);
> > > > +                   page = xdp_page;
> > >
> > > It seems we can limit the scope of xdp_page in this "else if" block.
> > >
> > > >             } else {
> > > >                     xdp_page = page;
> > > >             }
> > >
> > > It seems the above else block is not needed anymore.
> >
> > Yes, the follow-up patch has this optimization.
> >
> >
> > >
> > > > @@ -1278,8 +1284,6 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                     if (unlikely(!head_skb))
> > > >                             goto err_xdp_frags;
> > > >
> > > > -                   if (unlikely(xdp_page != page))
> > > > -                           put_page(page);
> > > >                     rcu_read_unlock();
> > > >                     return head_skb;
> > > >             case XDP_TX:
> > > > @@ -1297,8 +1301,6 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                             goto err_xdp_frags;
> > > >                     }
> > > >                     *xdp_xmit |= VIRTIO_XDP_TX;
> > > > -                   if (unlikely(xdp_page != page))
> > > > -                           put_page(page);
> > > >                     rcu_read_unlock();
> > > >                     goto xdp_xmit;
> > > >             case XDP_REDIRECT:
> > > > @@ -1307,8 +1309,6 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                     if (err)
> > > >                             goto err_xdp_frags;
> > > >                     *xdp_xmit |= VIRTIO_XDP_REDIR;
> > > > -                   if (unlikely(xdp_page != page))
> > > > -                           put_page(page);
> > > >                     rcu_read_unlock();
> > > >                     goto xdp_xmit;
> > > >             default:
> > > > @@ -1321,9 +1321,6 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
> > > >                     goto err_xdp_frags;
> > > >             }
> > > >  err_xdp_frags:
> > > > -           if (unlikely(xdp_page != page))
> > > > -                   __free_pages(xdp_page, 0);
> > >
> > > It seems __free_pages() and put_page() is used interchangeably here.
> > > Perhaps using __free_pages() have performance reason? As the comment below:
> > >
> > > https://elixir.bootlin.com/linux/v6.3-rc3/source/net/core/page_pool.c#L500
> >
> >
> > Yes, but now we don't seem to be very good to distinguish it. But I think
> > it doesn't matter. This logic is rare under actual situation.
> >
> > Thanks.
> >
> >
> > >
> > > > -
> > > >             if (xdp_buff_has_frags(&xdp)) {
> > > >                     shinfo = xdp_get_shared_info_from_buff(&xdp);
> > > >                     for (i = 0; i < shinfo->nr_frags; i++) {
> > > >
> >
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2023-03-23  5:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-22  3:03 [PATCH net-next 0/8] virtio_net: refactor xdp codes Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 1/8] virtio_net: mergeable xdp: put old page immediately Xuan Zhuo
     [not found]   ` <4bd07874-b1ad-336b-b15e-ba56a10182e9@huawei.com>
2023-03-23  1:36     ` Xuan Zhuo
     [not found]       ` <941a16c5-ba64-ca49-9af9-68d9615dca00@huawei.com>
2023-03-23  3:45         ` Xuan Zhuo
2023-03-23  5:38       ` Jason Wang
2023-03-23  5:58         ` Xuan Zhuo [this message]
2023-03-22  3:03 ` [PATCH net-next 2/8] virtio_net: mergeable xdp: introduce mergeable_xdp_prepare Xuan Zhuo
     [not found]   ` <c7749936-c154-da51-ccfb-f16150d19c62@huawei.com>
2023-03-23  1:45     ` Xuan Zhuo
     [not found]       ` <215e791d-1802-2419-ff59-49476bcdcd02@huawei.com>
2023-03-23  5:40         ` Jason Wang
     [not found]           ` <00509559-f3b6-2914-76f4-39e9e96f37c1@huawei.com>
2023-03-23 11:04             ` Xuan Zhuo
2023-03-23 10:59         ` Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 3/8] virtio_net: introduce virtnet_xdp_handler() to seprate the logic of run xdp Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 4/8] virtio_net: separate the logic of freeing xdp shinfo Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 5/8] virtio_net: separate the logic of freeing the rest mergeable buf Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 6/8] virtio_net: auto release xdp shinfo Xuan Zhuo
2023-03-22  3:03 ` [PATCH net-next 7/8] virtio_net: introduce receive_mergeable_xdp() Xuan Zhuo
2023-03-22 23:43   ` kernel test robot
2023-03-22  3:03 ` [PATCH net-next 8/8] virtio_net: introduce receive_small_xdp() Xuan Zhuo
2023-03-23  2:06   ` kernel test robot
2023-03-22  3:34 ` [PATCH net-next 0/8] virtio_net: refactor xdp codes Michael S. Tsirkin
2023-03-22  3:40   ` Xuan Zhuo
2023-03-22  3:53     ` Michael S. Tsirkin
2023-03-22  3:56       ` Xuan Zhuo
  -- strict thread matches above, loose matches on Subject: below --
2023-03-28 12:04 Xuan Zhuo
2023-03-28 12:04 ` [PATCH net-next 1/8] virtio_net: mergeable xdp: put old page immediately Xuan Zhuo
2023-03-31  9:01   ` Jason Wang
2023-04-03  4:11     ` Xuan Zhuo

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=1679551089.625654-2-xuanzhuo@linux.alibaba.com \
    --to=xuanzhuo@linux.alibaba.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hawk@kernel.org \
    --cc=jasowang@redhat.com \
    --cc=john.fastabend@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).