From: Igor Russkikh <irusskikh@marvell.com>
To: <netdev@vger.kernel.org>
Cc: Mark Starovoytov <mstarovoitov@marvell.com>,
Sabrina Dubroca <sd@queasysnail.net>,
Igor Russkikh <irusskikh@marvell.com>,
Antoine Tenart <antoine.tenart@bootlin.com>
Subject: [RFC v2 01/16] net: introduce the MACSEC netdev feature
Date: Tue, 10 Mar 2020 18:03:27 +0300 [thread overview]
Message-ID: <20200310150342.1701-2-irusskikh@marvell.com> (raw)
In-Reply-To: <20200310150342.1701-1-irusskikh@marvell.com>
From: Antoine Tenart <antoine.tenart@bootlin.com>
This patch introduce a new netdev feature, which will be used by drivers
to state they can perform MACsec transformations in hardware.
Signed-off-by: Antoine Tenart <antoine.tenart@bootlin.com>
Signed-off-by: Mark Starovoytov <mstarovoitov@marvell.com>
Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
---
include/linux/netdev_features.h | 3 +++
net/ethtool/common.c | 1 +
2 files changed, 4 insertions(+)
diff --git a/include/linux/netdev_features.h b/include/linux/netdev_features.h
index 34d050bb1ae6..9d53c5ad272c 100644
--- a/include/linux/netdev_features.h
+++ b/include/linux/netdev_features.h
@@ -83,6 +83,8 @@ enum {
NETIF_F_HW_TLS_RECORD_BIT, /* Offload TLS record */
NETIF_F_GRO_FRAGLIST_BIT, /* Fraglist GRO */
+ NETIF_F_HW_MACSEC_BIT, /* Offload MACsec operations */
+
/*
* Add your fresh new feature above and remember to update
* netdev_features_strings[] in net/core/ethtool.c and maybe
@@ -154,6 +156,7 @@ enum {
#define NETIF_F_HW_TLS_RX __NETIF_F(HW_TLS_RX)
#define NETIF_F_GRO_FRAGLIST __NETIF_F(GRO_FRAGLIST)
#define NETIF_F_GSO_FRAGLIST __NETIF_F(GSO_FRAGLIST)
+#define NETIF_F_HW_MACSEC __NETIF_F(HW_MACSEC)
/* Finds the next feature with the highest number of the range of start till 0.
*/
diff --git a/net/ethtool/common.c b/net/ethtool/common.c
index 7b6969af5ae7..686d3c7dce83 100644
--- a/net/ethtool/common.c
+++ b/net/ethtool/common.c
@@ -60,6 +60,7 @@ const char netdev_features_strings[NETDEV_FEATURE_COUNT][ETH_GSTRING_LEN] = {
[NETIF_F_HW_TLS_TX_BIT] = "tls-hw-tx-offload",
[NETIF_F_HW_TLS_RX_BIT] = "tls-hw-rx-offload",
[NETIF_F_GRO_FRAGLIST_BIT] = "rx-gro-list",
+ [NETIF_F_HW_MACSEC_BIT] = "macsec-hw-offload",
};
const char
--
2.17.1
next prev parent reply other threads:[~2020-03-10 15:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 15:03 [RFC v2 00/16] net: atlantic: MACSec support for AQC devices Igor Russkikh
2020-03-10 15:03 ` Igor Russkikh [this message]
2020-03-10 15:03 ` [RFC v2 02/16] net: add a reference to MACsec ops in net_device Igor Russkikh
2020-03-10 15:03 ` [RFC v2 03/16] net: macsec: allow to reference a netdev from a MACsec context Igor Russkikh
2020-03-10 15:03 ` [RFC v2 04/16] net: macsec: add support for offloading to the MAC Igor Russkikh
2020-03-10 15:03 ` [RFC v2 05/16] net: macsec: init secy pointer in macsec_context Igor Russkikh
2020-03-10 15:03 ` [RFC v2 06/16] net: macsec: allow multiple macsec devices with offload Igor Russkikh
2020-03-10 15:03 ` [RFC v2 07/16] net: macsec: support multicast/broadcast when offloading Igor Russkikh
2020-03-10 15:03 ` [RFC v2 08/16] net: macsec: add support for getting offloaded stats Igor Russkikh
2020-03-10 15:03 ` [RFC v2 09/16] net: macsec: report real_dev features when HW offloading is enabled Igor Russkikh
2020-03-10 15:03 ` [RFC v2 10/16] net: atlantic: MACSec offload skeleton Igor Russkikh
2020-03-10 15:03 ` [RFC v2 11/16] net: atlantic: MACSec egress offload HW bindings Igor Russkikh
2020-03-10 15:03 ` [RFC v2 12/16] net: atlantic: MACSec egress offload implementation Igor Russkikh
2020-03-10 15:03 ` [RFC v2 13/16] net: atlantic: MACSec ingress offload HW bindings Igor Russkikh
2020-03-10 15:03 ` [RFC v2 14/16] net: atlantic: MACSec ingress offload implementation Igor Russkikh
2020-03-10 15:03 ` [RFC v2 15/16] net: atlantic: MACSec offload statistics HW bindings Igor Russkikh
2020-03-10 15:03 ` [RFC v2 16/16] net: atlantic: MACSec offload statistics implementation Igor Russkikh
2020-03-11 8:36 ` [EXT] [RFC v2 00/16] net: atlantic: MACSec support for AQC devices Igor Russkikh
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=20200310150342.1701-2-irusskikh@marvell.com \
--to=irusskikh@marvell.com \
--cc=antoine.tenart@bootlin.com \
--cc=mstarovoitov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
/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).