From: Heng Qi <hengqi@linux.alibaba.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [RFC PATCH 6/9] virtio_net: construct multi-buffer xdp in mergeable
Date: Thu, 8 Dec 2022 16:30:00 +0800 [thread overview]
Message-ID: <8b143235-2e74-eddf-4c22-a36d679d093e@linux.alibaba.com> (raw)
In-Reply-To: <CACGkMEsbX8w1wuU+954zVwNT5JvCHX7a9baKRytVb641UmNsuw@mail.gmail.com>
在 2022/12/6 下午2:33, Jason Wang 写道:
> On Tue, Nov 22, 2022 at 3:44 PM Heng Qi <hengqi@linux.alibaba.com> wrote:
>> Build multi-buffer xdp using virtnet_build_xdp_buff() in mergeable.
>>
>> For the prefilled buffer before xdp is set, vq reset can be
>> used to clear it, but most devices do not support it at present.
>> In order not to bother users who are using xdp normally, we do
>> not use vq reset for the time being.
> I guess to tweak the part to say we will probably use vq reset in the future.
OK, it works.
>
>> At the same time, virtio
>> net currently uses comp pages, and bpf_xdp_frags_increase_tail()
>> needs to calculate the tailroom of the last frag, which will
>> involve the offset of the corresponding page and cause a negative
>> value, so we disable tail increase by not setting xdp_rxq->frag_size.
>>
>> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
>> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>> ---
>> drivers/net/virtio_net.c | 67 +++++++++++++++++++++++-----------------
>> 1 file changed, 38 insertions(+), 29 deletions(-)
>>
>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>> index 20784b1d8236..83e6933ae62b 100644
>> --- a/drivers/net/virtio_net.c
>> +++ b/drivers/net/virtio_net.c
>> @@ -994,6 +994,7 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
>> unsigned int *xdp_xmit,
>> struct virtnet_rq_stats *stats)
>> {
>> + unsigned int tailroom = SKB_DATA_ALIGN(sizeof(struct skb_shared_info));
>> struct virtio_net_hdr_mrg_rxbuf *hdr = buf;
>> u16 num_buf = virtio16_to_cpu(vi->vdev, hdr->num_buffers);
>> struct page *page = virt_to_head_page(buf);
>> @@ -1024,53 +1025,50 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
>> rcu_read_lock();
>> xdp_prog = rcu_dereference(rq->xdp_prog);
>> if (xdp_prog) {
>> + unsigned int xdp_frags_truesz = 0;
>> + struct skb_shared_info *shinfo;
>> struct xdp_frame *xdpf;
>> struct page *xdp_page;
>> struct xdp_buff xdp;
>> void *data;
>> u32 act;
>> + int i;
>>
>> - /* Transient failure which in theory could occur if
>> - * in-flight packets from before XDP was enabled reach
>> - * the receive path after XDP is loaded.
>> - */
>> - if (unlikely(hdr->hdr.gso_type))
>> - goto err_xdp;
> Two questions:
>
> 1) should we keep this check for the XDP program that can't deal with XDP frags?
Yes, the problem is the same as the xdp program without xdp.frags when
GRO_HW, I will correct it.
> 2) how could we guarantee that the vnet header (gso_type/csum_start
> etc) is still valid after XDP (where XDP program can choose to
> override the header)?
We can save the vnet headr before the driver receives the packet and
build xdp_buff, and then use
the pre-saved value in the subsequent process.
>> -
>> - /* Buffers with headroom use PAGE_SIZE as alloc size,
>> - * see add_recvbuf_mergeable() + get_mergeable_buf_len()
>> + /* Now XDP core assumes frag size is PAGE_SIZE, but buffers
>> + * with headroom may add hole in truesize, which
>> + * make their length exceed PAGE_SIZE. So we disabled the
>> + * hole mechanism for xdp. See add_recvbuf_mergeable().
>> */
>> frame_sz = headroom ? PAGE_SIZE : truesize;
>>
>> - /* This happens when rx buffer size is underestimated
>> - * or headroom is not enough because of the buffer
>> - * was refilled before XDP is set. This should only
>> - * happen for the first several packets, so we don't
>> - * care much about its performance.
>> + /* This happens when headroom is not enough because
>> + * of the buffer was prefilled before XDP is set.
>> + * This should only happen for the first several packets.
>> + * In fact, vq reset can be used here to help us clean up
>> + * the prefilled buffers, but many existing devices do not
>> + * support it, and we don't want to bother users who are
>> + * using xdp normally.
>> */
>> - if (unlikely(num_buf > 1 ||
>> - headroom < virtnet_get_headroom(vi))) {
>> - /* linearize data for XDP */
>> - xdp_page = xdp_linearize_page(rq, &num_buf,
>> - page, offset,
>> - VIRTIO_XDP_HEADROOM,
>> - &len);
>> - frame_sz = PAGE_SIZE;
>> + if (unlikely(headroom < virtnet_get_headroom(vi))) {
>> + if ((VIRTIO_XDP_HEADROOM + len + tailroom) > PAGE_SIZE)
>> + goto err_xdp;
>>
>> + xdp_page = alloc_page(GFP_ATOMIC);
>> if (!xdp_page)
>> goto err_xdp;
>> +
>> + memcpy(page_address(xdp_page) + VIRTIO_XDP_HEADROOM,
>> + page_address(page) + offset, len);
>> + frame_sz = PAGE_SIZE;
> How can we know a single page is sufficient here? (before XDP is set,
> we reserve neither headroom nor tailroom).
This is only for the first buffer, refer to add_recvbuf_mergeable() and
get_mergeable_buf_len() A buffer is always no larger than a page.
>
>> offset = VIRTIO_XDP_HEADROOM;
> I think we should still try to do linearization for the XDP program
> that doesn't support XDP frags.
Yes, you are right.
Thanks.
>
> Thanks
>
>> } else {
>> xdp_page = page;
>> }
>> -
>> - /* Allow consuming headroom but reserve enough space to push
>> - * the descriptor on if we get an XDP_TX return code.
>> - */
>> data = page_address(xdp_page) + offset;
>> - xdp_init_buff(&xdp, frame_sz - vi->hdr_len, &rq->xdp_rxq);
>> - xdp_prepare_buff(&xdp, data - VIRTIO_XDP_HEADROOM + vi->hdr_len,
>> - VIRTIO_XDP_HEADROOM, len - vi->hdr_len, true);
>> + err = virtnet_build_xdp_buff(dev, vi, rq, &xdp, data, len, frame_sz,
>> + &num_buf, &xdp_frags_truesz, stats);
>> + if (unlikely(err))
>> + goto err_xdp_frags;
>>
>> act = bpf_prog_run_xdp(xdp_prog, &xdp);
>> stats->xdp_packets++;
>> @@ -1164,6 +1162,17 @@ static struct sk_buff *receive_mergeable(struct net_device *dev,
>> __free_pages(xdp_page, 0);
>> goto err_xdp;
>> }
>> +err_xdp_frags:
>> + shinfo = xdp_get_shared_info_from_buff(&xdp);
>> +
>> + if (unlikely(xdp_page != page))
>> + __free_pages(xdp_page, 0);
>> +
>> + for (i = 0; i < shinfo->nr_frags; i++) {
>> + xdp_page = skb_frag_page(&shinfo->frags[i]);
>> + put_page(xdp_page);
>> + }
>> + goto err_xdp;
>> }
>> rcu_read_unlock();
>>
>> --
>> 2.19.1.6.gb485710b
>>
next prev parent reply other threads:[~2022-12-08 8:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 7:43 [RFC PATCH 0/9] virtio_net: support multi buffer xdp Heng Qi
2022-11-22 7:43 ` [RFC PATCH 1/9] virtio_net: disable the hole mechanism for xdp Heng Qi
2022-12-06 5:20 ` Jason Wang
2022-12-08 8:20 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 2/9] virtio_net: set up xdp for multi buffer packets Heng Qi
2022-12-06 5:29 ` Jason Wang
2022-12-08 8:21 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 3/9] virtio_net: update bytes calculation for xdp_frame Heng Qi
2022-12-06 5:31 ` Jason Wang
2022-12-08 8:35 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 4/9] virtio_net: remove xdp related info from page_to_skb() Heng Qi
2022-12-06 5:36 ` Jason Wang
2022-12-08 8:23 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 5/9] virtio_net: build xdp_buff with multi buffers Heng Qi
2022-12-06 6:14 ` Jason Wang
2022-12-08 8:25 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 6/9] virtio_net: construct multi-buffer xdp in mergeable Heng Qi
2022-12-06 6:33 ` Jason Wang
2022-12-08 8:30 ` Heng Qi [this message]
2022-12-13 7:08 ` Jason Wang
2022-12-14 8:37 ` Heng Qi
2022-12-16 3:46 ` Jason Wang
2022-12-16 9:42 ` Heng Qi
2022-11-22 7:43 ` [RFC PATCH 7/9] virtio_net: build skb from multi-buffer xdp Heng Qi
2022-11-22 7:43 ` [RFC PATCH 8/9] virtio_net: transmit the " Heng Qi
2022-11-22 7:43 ` [RFC PATCH 9/9] virtio_net: support " Heng Qi
2022-12-06 6:42 ` Jason Wang
2022-12-08 8:31 ` Heng Qi
2022-12-02 4:50 ` [RFC PATCH 0/9] virtio_net: support multi buffer xdp Heng Qi
2022-12-02 5:41 ` 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=8b143235-2e74-eddf-4c22-a36d679d093e@linux.alibaba.com \
--to=hengqi@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=jasowang@redhat.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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