netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, saeedm@mellanox.com,
	michael.chan@broadcom.com, emil.s.tantilov@intel.com,
	alexander.h.duyck@linux.intel.com, jeffrey.t.kirsher@intel.com,
	tariqt@mellanox.com, mkubecek@suse.cz,
	Jakub Kicinski <kuba@kernel.org>
Subject: [PATCH net-next v4 02/10] udp_tunnel: re-number the offload tunnel types
Date: Thu,  9 Jul 2020 17:42:45 -0700	[thread overview]
Message-ID: <20200710004253.211130-3-kuba@kernel.org> (raw)
In-Reply-To: <20200710004253.211130-1-kuba@kernel.org>

Make it possible to use tunnel types as flags more easily.
There doesn't appear to be any user using the type as an
array index, so this should make no difference.

Signed-off-by: Jakub Kicinski <kuba@kernel.org>
---
 include/net/udp_tunnel.h | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/include/net/udp_tunnel.h b/include/net/udp_tunnel.h
index e7312ceb2794..0615e25f041c 100644
--- a/include/net/udp_tunnel.h
+++ b/include/net/udp_tunnel.h
@@ -106,9 +106,9 @@ void setup_udp_tunnel_sock(struct net *net, struct socket *sock,
  * call this function to perform Tx offloads on outgoing traffic.
  */
 enum udp_parsable_tunnel_type {
-	UDP_TUNNEL_TYPE_VXLAN,		/* RFC 7348 */
-	UDP_TUNNEL_TYPE_GENEVE,		/* draft-ietf-nvo3-geneve */
-	UDP_TUNNEL_TYPE_VXLAN_GPE,	/* draft-ietf-nvo3-vxlan-gpe */
+	UDP_TUNNEL_TYPE_VXLAN	  = BIT(0), /* RFC 7348 */
+	UDP_TUNNEL_TYPE_GENEVE	  = BIT(1), /* draft-ietf-nvo3-geneve */
+	UDP_TUNNEL_TYPE_VXLAN_GPE = BIT(2), /* draft-ietf-nvo3-vxlan-gpe */
 };
 
 struct udp_tunnel_info {
-- 
2.26.2


  parent reply	other threads:[~2020-07-10  0:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  0:42 [PATCH net-next v4 00/10] udp_tunnel: add NIC RX port offload infrastructure Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 01/10] debugfs: make sure we can remove u32_array files cleanly Jakub Kicinski
2020-07-10  0:42 ` Jakub Kicinski [this message]
2020-07-10  0:42 ` [PATCH net-next v4 03/10] udp_tunnel: add central NIC RX port offload infrastructure Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 04/10] ethtool: add tunnel info interface Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 05/10] netdevsim: add UDP tunnel port offload support Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 06/10] selftests: net: add a test for UDP tunnel info infra Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 07/10] ixgbe: don't clear UDP tunnel ports when RXCSUM is disabled Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 08/10] ixgbe: convert to new udp_tunnel_nic infra Jakub Kicinski
2020-07-10  0:42 ` [PATCH net-next v4 09/10] bnxt: " Jakub Kicinski
2020-07-10  1:50   ` Michael Chan
2020-07-10  0:42 ` [PATCH net-next v4 10/10] mlx4: " Jakub Kicinski
2020-07-10 20:54 ` [PATCH net-next v4 00/10] udp_tunnel: add NIC RX port offload infrastructure 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=20200710004253.211130-3-kuba@kernel.org \
    --to=kuba@kernel.org \
    --cc=alexander.h.duyck@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=emil.s.tantilov@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=michael.chan@broadcom.com \
    --cc=mkubecek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@mellanox.com \
    --cc=tariqt@mellanox.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).