From: John Hurley <john.hurley@netronome.com>
To: netdev@vger.kernel.org, davem@davemloft.net,
oss-drivers@netronome.com, jakub.kicinski@netronome.com
Cc: John Hurley <john.hurley@netronome.com>
Subject: [PATCH net-next 1/3] net: add netif_is_geneve()
Date: Wed, 7 Nov 2018 18:32:48 +0000 [thread overview]
Message-ID: <1541615570-523-2-git-send-email-john.hurley@netronome.com> (raw)
In-Reply-To: <1541615570-523-1-git-send-email-john.hurley@netronome.com>
Add a helper function to determine if the type of a netdev is geneve based
on its rtnl_link_ops. This allows drivers that may wish to offload tunnels
to check the underlying type of the device.
A recent patch added a similar helper to vxlan.h
Signed-off-by: John Hurley <john.hurley@netronome.com>
Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com>
---
include/net/geneve.h | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/include/net/geneve.h b/include/net/geneve.h
index a7600ed..fc6a7e0 100644
--- a/include/net/geneve.h
+++ b/include/net/geneve.h
@@ -60,6 +60,12 @@ struct genevehdr {
struct geneve_opt options[];
};
+static inline bool netif_is_geneve(const struct net_device *dev)
+{
+ return dev->rtnl_link_ops &&
+ !strcmp(dev->rtnl_link_ops->kind, "geneve");
+}
+
#ifdef CONFIG_INET
struct net_device *geneve_dev_create_fb(struct net *net, const char *name,
u8 name_assign_type, u16 dst_port);
--
2.7.4
next prev parent reply other threads:[~2018-11-08 4:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 18:32 [PATCH net-next 0/3] nfp: add and use tunnel netdev helpers John Hurley
2018-11-07 18:32 ` John Hurley [this message]
2018-11-07 18:32 ` [PATCH net-next 2/3] nfp: flower: use geneve and vxlan helpers John Hurley
2018-11-07 18:32 ` [PATCH net-next 3/3] nfp: flower: include geneve as supported offload tunnel type John Hurley
2018-11-08 7:00 ` [PATCH net-next 0/3] nfp: add and use tunnel netdev helpers 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=1541615570-523-2-git-send-email-john.hurley@netronome.com \
--to=john.hurley@netronome.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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).