From: Jason Wang <jasowang@redhat.com>
To: Daniel Borkmann <daniel@iogearbox.net>
Cc: davem@davemloft.net, mst@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, kubakici@wp.pl
Subject: Re: [PATCH net-next V2 3/3] tap: XDP support
Date: Tue, 15 Aug 2017 12:55:37 +0800 [thread overview]
Message-ID: <3bc5f71d-5a2c-5b59-037c-b0c2365bbe93@redhat.com> (raw)
In-Reply-To: <599162CA.4080504@iogearbox.net>
On 2017年08月14日 16:43, Daniel Borkmann wrote:
> On 08/11/2017 01:41 PM, Jason Wang wrote:
>> This patch tries to implement XDP for tun. The implementation was
>> split into two parts:
> [...]
>> @@ -1402,6 +1521,22 @@ static ssize_t tun_get_user(struct tun_struct
>> *tun, struct tun_file *tfile,
>> skb_reset_network_header(skb);
>> skb_probe_transport_header(skb, 0);
>>
>> + if (generic_xdp) {
>> + struct bpf_prog *xdp_prog;
>> + int ret;
>> +
>> + rcu_read_lock();
>> + xdp_prog = rcu_dereference(tun->xdp_prog);
>
> The name generic_xdp is a bit confusing in this context given this
> is 'native' XDP, perhaps above if (generic_xdp) should have a comment
> explaining semantics for tun and how it relates to actual generic xdp
> that sits at dev->xdp_prog, and gets run from netif_rx_ni(). Or just
> name the bool xdp_handle_gso with a comment that we let the generic
> XDP infrastructure deal with non-linear skbs instead of having to
> re-implement the do_xdp_generic() internals, plus a statement that
> the actual generic XDP comes a bit later in the path. That would at
> least make it more obvious to read, imho.
Ok, since non gso packet (e.g jumbo packet) may go this way too,
something like "xdp_handle_skb" is better. Will send a patch.
Thanks
>
>> + if (xdp_prog) {
>> + ret = do_xdp_generic(xdp_prog, skb);
>> + if (ret != XDP_PASS) {
>> + rcu_read_unlock();
>> + return total_len;
>> + }
>> + }
>> + rcu_read_unlock();
>> + }
>> +
>> rxhash = __skb_get_hash_symmetric(skb);
>> #ifndef CONFIG_4KSTACKS
>> tun_rx_batched(tun, tfile, skb, more);
>>
>
next prev parent reply other threads:[~2017-08-15 4:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 11:41 [PATCH net-next V2 0/3] XDP support for tap Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 1/3] tap: use build_skb() for small packet Jason Wang
2017-08-16 3:45 ` Eric Dumazet
2017-08-16 3:55 ` Michael S. Tsirkin
2017-08-16 3:57 ` Jason Wang
2017-08-16 3:59 ` Michael S. Tsirkin
2017-08-16 4:07 ` Jason Wang
2017-08-16 9:17 ` Jason Wang
2017-08-16 16:30 ` David Miller
2017-08-16 3:55 ` Jason Wang
2017-08-16 10:24 ` Eric Dumazet
2017-08-16 13:16 ` Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 2/3] net: export some generic xdp helpers Jason Wang
2017-08-11 11:41 ` [PATCH net-next V2 3/3] tap: XDP support Jason Wang
2017-08-11 23:12 ` Jakub Kicinski
2017-08-12 2:48 ` Jason Wang
2017-08-14 16:01 ` Michael S. Tsirkin
2017-08-15 5:02 ` Jason Wang
2017-08-16 3:45 ` Michael S. Tsirkin
2017-08-14 8:43 ` Daniel Borkmann
2017-08-15 4:55 ` Jason Wang [this message]
2017-08-14 2:56 ` [PATCH net-next V2 0/3] XDP support for tap David Miller
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=3bc5f71d-5a2c-5b59-037c-b0c2365bbe93@redhat.com \
--to=jasowang@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kubakici@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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).