From: Jason Wang <jasowang@redhat.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, jbrouer@redhat.com,
mst@redhat.com, Jason Wang <jasowang@redhat.com>
Subject: [RFC PATCH net-next 1/5] net: core: generic XDP support for stacked device
Date: Mon, 13 Aug 2018 11:05:09 +0800 [thread overview]
Message-ID: <1534129513-4845-2-git-send-email-jasowang@redhat.com> (raw)
In-Reply-To: <1534129513-4845-1-git-send-email-jasowang@redhat.com>
Stacked device usually change skb->dev to its own and return
RX_HANDLER_ANOTHER during rx handler processing. But we don't call
generic XDP routine at that time, this means it can't work for stacked
device.
Fixing this by calling netif_do_generic_xdp() if rx handler returns
RX_HANDLER_ANOTHER. This allows us to do generic XDP on stacked device
e.g macvlan.
Signed-off-by: Jason Wang <jasowang@redhat.com>
---
net/core/dev.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/net/core/dev.c b/net/core/dev.c
index 605c66e..a77ce08 100644
--- a/net/core/dev.c
+++ b/net/core/dev.c
@@ -4822,6 +4822,11 @@ static int __netif_receive_skb_core(struct sk_buff *skb, bool pfmemalloc,
ret = NET_RX_SUCCESS;
goto out;
case RX_HANDLER_ANOTHER:
+ ret = netif_do_generic_xdp(skb);
+ if (ret != XDP_PASS) {
+ ret = NET_RX_SUCCESS;
+ goto out;
+ }
goto another_round;
case RX_HANDLER_EXACT:
deliver_exact = true;
--
2.7.4
next prev parent reply other threads:[~2018-08-13 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 3:05 [RFC PATCH net-next 0/5] XDP rx handler Jason Wang
2018-08-13 3:05 ` Jason Wang [this message]
2018-08-13 3:05 ` [RFC PATCH net-next 2/5] net: core: introduce " Jason Wang
2018-08-13 3:05 ` [RFC PATCH net-next 3/5] macvlan: count the number of vlan in source mode Jason Wang
2018-08-13 3:05 ` [RFC PATCH net-next 4/5] macvlan: basic XDP support Jason Wang
2018-08-13 3:05 ` [RFC PATCH net-next 5/5] virtio-net: support XDP rx handler Jason Wang
2018-08-13 3:17 ` [RFC PATCH net-next 0/5] " 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=1534129513-4845-2-git-send-email-jasowang@redhat.com \
--to=jasowang@redhat.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=jbrouer@redhat.com \
--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).