[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ba0c0d5f-fbb4-ff92-c7d8-403dbb757758@gmail.com>
Date: Mon, 9 Dec 2019 09:24:34 +0900
From: Prashant Bhole <prashantbhole.linux@...il.com>
To: Jason Wang <jasowang@...hat.com>, David Ahern <dsahern@...il.com>,
"David S . Miller" <davem@...emloft.net>,
"Michael S . Tsirkin" <mst@...hat.com>,
Alexei Starovoitov <ast@...nel.org>,
Jakub Kicinski <jakub.kicinski@...ronome.com>
Cc: Daniel Borkmann <daniel@...earbox.net>,
Jesper Dangaard Brouer <hawk@...nel.org>,
John Fastabend <john.fastabend@...il.com>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
Andrii Nakryiko <andriin@...com>, netdev@...r.kernel.org,
qemu-devel@...gnu.org, kvm@...r.kernel.org
Subject: Re: [RFC net-next 07/18] tun: set offloaded xdp program
On 12/2/19 11:47 AM, Jason Wang wrote:
>
> On 2019/12/2 上午12:45, David Ahern wrote:
>> On 11/26/19 4:07 AM, Prashant Bhole wrote:
>>> From: Jason Wang <jasowang@...hat.com>
>>>
>>> This patch introduces an ioctl way to set an offloaded XDP program
>>> to tun driver. This ioctl will be used by qemu to offload XDP program
>>> from virtio_net in the guest.
>>>
>> Seems like you need to set / reset the SOCK_XDP flag on tfile->sk since
>> this is an XDP program.
>>
>> Also, why not add this program using netlink instead of ioctl? e.g., as
>> part of a generic XDP in the egress path like I am looking into for the
>> host side.
>
>
> Maybe both, otherwise, qemu may need netlink as a dependency.
>
> Thanks
>
Thank you all for reviewing. We will continue to improve this set.
If we split this work, Tx path XDP is one of the necessary part
which can be developed first. As suggested by David Ahern it will be
a netlink way but we will still need ioctl way for tap. I will try
to come up with Tx path XDP set next time.
Thanks.
Powered by blists - more mailing lists