From: Leon Romanovsky <leon@kernel.org>
To: Lior Nahmanson <liorna@nvidia.com>
Cc: edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next v1 00/3] Introduce MACsec offload SKB extension
Date: Sun, 8 May 2022 18:40:35 +0300 [thread overview]
Message-ID: <Ynfkc7CxqF29VTBv@unreal> (raw)
In-Reply-To: <20220508090954.10864-1-liorna@nvidia.com>
On Sun, May 08, 2022 at 12:09:51PM +0300, Lior Nahmanson wrote:
> This patchset introduces MACsec SKB extension to lay the ground
> for MACsec HW offload.
>
> MACsec is an IEEE standard (IEEE 802.1AE) for MAC security.
> It defines a way to establish a protocol independent connection
> between two hosts with data confidentiality, authenticity and/or
> integrity, using GCM-AES. MACsec operates on the Ethernet layer and
> as such is a layer 2 protocol, which means it’s designed to secure
> traffic within a layer 2 network, including DHCP or ARP requests.
>
> Linux has a software implementation of the MACsec standard and
> HW offloading support.
> The offloading is re-using the logic, netlink API and data
> structures of the existing MACsec software implementation.
>
> For Tx:
> In the current MACsec offload implementation, MACsec interfaces are
> sharing the same MAC address of their parent interface by default.
> Therefore, HW can't distinguish if a packet was sent from MACsec
> interface and need to be offloaded or not.
> Also, it can't distinguish from which MACsec interface it was sent in
> case there are multiple MACsec interface with the same MAC address.
>
> Used SKB extension, so SW can mark if a packet is needed to be offloaded
> and use the SCI, which is unique value for each MACsec interface,
> to notify the HW from which MACsec interface the packet is sent.
>
> For Rx:
> Like in the Tx changes, packet that don't have SecTAG
> header aren't necessary been offloaded by the HW.
> Therefore, the MACsec driver needs to distinguish if the packet
> was offloaded or not and handle accordingly.
> Moreover, if there are more than one MACsec device with the same MAC
> address as in the packet's destination MAC, the packet will forward only
> to this device and only to the desired one.
>
> Used SKB extension and marking it by the HW if the packet was offloaded
> and to which MACsec offload device it belongs according to the packet's
> SCI.
>
> 1) patch 0001-0002, Add support to SKB extension in MACsec code:
> net/macsec: Add MACsec skb extension Tx Data path support
> net/macsec: Add MACsec skb extension Rx Data path support
>
> 2) patch 0003, Move some MACsec driver code for sharing with various
> drivers that implements offload:
> net/macsec: Move some code for sharing with various drivers that
> implements offload
Can you please post diffstat and patch list of the series?
As a reply to this cover letter.
As an example:
https://lore.kernel.org/netdev/20220508153049.427227-1-andrew@lunn.ch/T/#m3c6fbfaa6c4e8c841e8bbb7e8953daefd2a53cd9
Thanks
next prev parent reply other threads:[~2022-05-08 15:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 9:09 [PATCH net-next v1 00/3] Introduce MACsec offload SKB extension Lior Nahmanson
2022-05-08 9:09 ` [PATCH net-next v1 01/03] net/macsec: Add MACsec skb extension Tx Data path support Lior Nahmanson
2022-05-10 9:23 ` Paolo Abeni
2022-05-19 6:26 ` Lior Nahmanson
2022-05-08 9:09 ` [PATCH net-next v1 02/03] net/macsec: Add MACsec skb extension Rx " Lior Nahmanson
2022-05-08 9:09 ` [PATCH net-next v1 03/03] net/macsec: Move some code for sharing with various drivers that implements offload Lior Nahmanson
2022-05-08 15:40 ` Leon Romanovsky [this message]
2022-05-09 6:41 ` [PATCH net-next v1 00/3] Introduce MACsec offload SKB extension Lior Nahmanson
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=Ynfkc7CxqF29VTBv@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=liorna@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.