From: Jason Wang <jasowang@redhat.com>
To: Heng Qi <hengqi@linux.alibaba.com>,
netdev@vger.kernel.org, bpf@vger.kernel.org
Cc: "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>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Subject: Re: [PATCH v2 2/9] virtio_net: set up xdp for multi buffer packets
Date: Wed, 28 Dec 2022 14:27:35 +0800 [thread overview]
Message-ID: <2af5c632-9d76-fc80-cf54-0b925a8b7069@redhat.com> (raw)
In-Reply-To: <d2b1f378-e30a-2b54-b8da-e9eb874badee@linux.alibaba.com>
在 2022/12/28 11:50, Heng Qi 写道:
>
>
> 在 2022/12/27 下午8:20, Heng Qi 写道:
>>
>>
>> 在 2022/12/27 下午2:32, Jason Wang 写道:
>>>
>>> 在 2022/12/20 22:14, Heng Qi 写道:
>>>> When the xdp program sets xdp.frags, which means it can process
>>>> multi-buffer packets over larger MTU, so we continue to support xdp.
>>>> But for single-buffer xdp, we should keep checking for MTU.
>>>>
>>>> Signed-off-by: Heng Qi <hengqi@linux.alibaba.com>
>>>> Reviewed-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
>>>> ---
>>>> drivers/net/virtio_net.c | 4 ++--
>>>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
>>>> index 443aa7b8f0ad..c5c4e9db4ed3 100644
>>>> --- a/drivers/net/virtio_net.c
>>>> +++ b/drivers/net/virtio_net.c
>>>> @@ -3095,8 +3095,8 @@ static int virtnet_xdp_set(struct net_device
>>>> *dev, struct bpf_prog *prog,
>>>> return -EINVAL;
>>>> }
>>>> - if (dev->mtu > max_sz) {
>>>> - NL_SET_ERR_MSG_MOD(extack, "MTU too large to enable XDP");
>>>> + if (prog && !prog->aux->xdp_has_frags && dev->mtu > max_sz) {
>>>
>>>
>>> Not related to this patch, but I see:
>>>
>>> unsigned long int max_sz = PAGE_SIZE - sizeof(struct
>>> padded_vnet_hdr);
>>>
>>> Which is suspicious, do we need to count reserved headroom/tailroom
>>> as well?
>>
>> This seems to be suspicious. After loading xdp, the size of the
>> filled avail buffer
>> is (PAGE_SIZE - headroom - tailroom), so the size of the received
>> used buffer, ie MTU,
>> should also be (PAGE_SIZE - headroom - tailroom).
>
> Hi Jason, this is indeed a problem. After verification, packet drop
> will indeed occur. To avoid this,
> the size of MTU should be (PAGE_SIZE - headroom - tailroom - ethhdr =
> 4096 - 256 -320 - 14 =3506).
> Because when there is xdp, each filling is 3520 (PAGE_SIZE - room), if
> the value of (MTU + 14) is
> greater than 3520 (because the MTU does not contain the ethernet
> header), then the packet with a
> length greater than 3520 will come in, so num_buf will still be
> greater than or equal to 2, and then
> xdp_linearize_page() will be performed and the packet will be dropped
> because the total length is
> greater than PAGE_SIZE.
>
> I will make a separate bugfix patch to fix this later.
Great.
Thanks
>
> Thanks.
>
>>
>> Thanks.
>>
>>>
>>> Thanks
>>>
>>>
>>>> + NL_SET_ERR_MSG_MOD(extack, "MTU too large to enable XDP
>>>> without frags");
>>>> netdev_warn(dev, "XDP requires MTU less than %lu\n",
>>>> max_sz);
>>>> return -EINVAL;
>>>> }
>
next prev parent reply other threads:[~2022-12-28 6:28 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 14:14 [PATCH v2 0/9] virtio_net: support multi buffer xdp Heng Qi
2022-12-20 14:14 ` [PATCH v2 1/9] virtio_net: disable the hole mechanism for xdp Heng Qi
2022-12-27 6:30 ` Jason Wang
2022-12-27 7:32 ` Heng Qi
2022-12-28 6:28 ` Jason Wang
2022-12-28 8:24 ` Heng Qi
2022-12-20 14:14 ` [PATCH v2 2/9] virtio_net: set up xdp for multi buffer packets Heng Qi
2022-12-27 6:32 ` Jason Wang
2022-12-27 12:20 ` Heng Qi
2022-12-28 3:50 ` Heng Qi
2022-12-28 6:27 ` Jason Wang [this message]
2022-12-20 14:14 ` [PATCH v2 3/9] virtio_net: update bytes calculation for xdp_frame Heng Qi
2022-12-20 14:14 ` [PATCH v2 4/9] virtio_net: build xdp_buff with multi buffers Heng Qi
2022-12-27 6:46 ` Jason Wang
2022-12-27 9:10 ` Heng Qi
2022-12-28 6:27 ` Jason Wang
2022-12-28 8:17 ` Heng Qi
2022-12-20 14:14 ` [PATCH v2 5/9] virtio_net: construct multi-buffer xdp in mergeable Heng Qi
2022-12-27 7:01 ` Jason Wang
2022-12-27 9:31 ` Heng Qi
2022-12-28 6:24 ` Jason Wang
2022-12-28 8:23 ` Heng Qi
2022-12-28 11:54 ` Jason Wang
2022-12-20 14:14 ` [PATCH v2 6/9] virtio_net: transmit the multi-buffer xdp Heng Qi
2022-12-27 7:12 ` Jason Wang
2022-12-27 8:26 ` Heng Qi
2022-12-28 6:30 ` Jason Wang
2022-12-28 8:25 ` Heng Qi
2022-12-20 14:14 ` [PATCH v2 7/9] virtio_net: build skb from " Heng Qi
2022-12-27 7:31 ` Jason Wang
2022-12-27 7:51 ` Heng Qi
2022-12-20 14:14 ` [PATCH v2 8/9] virtio_net: remove xdp related info from page_to_skb() Heng Qi
2022-12-27 7:55 ` Jason Wang
2022-12-27 8:27 ` Heng Qi
2022-12-20 14:14 ` [PATCH v2 9/9] virtio_net: support multi-buffer xdp Heng Qi
2022-12-27 9:03 ` Jason Wang
2022-12-27 9:11 ` Heng Qi
2022-12-22 1:30 ` [PATCH v2 0/9] virtio_net: support multi buffer xdp Jakub Kicinski
2022-12-22 2:04 ` Heng Qi
2022-12-26 2:32 ` Heng Qi
2022-12-26 4:14 ` 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=2af5c632-9d76-fc80-cf54-0b925a8b7069@redhat.com \
--to=jasowang@redhat.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hengqi@linux.alibaba.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).