From: David Ahern <dsahern@gmail.com>
To: Igor Russkikh <irusskikh@marvell.com>, netdev@vger.kernel.org
Cc: dsahern@gmail.com, stephen@networkplumber.org,
Mark Starovoytov <mstarovoitov@marvell.com>
Subject: Re: [PATCH iproute2-next 0/2] macsec: add offloading support
Date: Sun, 26 Apr 2020 12:33:14 -0600 [thread overview]
Message-ID: <0a44a226-0890-c856-58dd-b16e8b83c9dc@gmail.com> (raw)
In-Reply-To: <20200424083857.1265-1-irusskikh@marvell.com>
On 4/24/20 2:38 AM, Igor Russkikh wrote:
> From: Mark Starovoytov <mstarovoitov@marvell.com>
>
> This series adds support for selecting the offloading mode of a MACsec
> interface at link creation time.
> Available modes are for now 'off', 'phy' and 'mac', 'off' being the default
> when an interface is created.
>
> First patch adds support for MAC offloading.
>
> Last patch allows a user to change the offloading mode at runtime
> through a new attribute, `ip link add link ... offload`:
>
> # ip link add link enp1s0 type macsec encrypt on offload off
> # ip link add link enp1s0 type macsec encrypt on offload phy
> # ip link add link enp1s0 type macsec encrypt on offload mac
>
> Mark Starovoytov (2):
> macsec: add support for MAC offload
> macsec: add support for specifying offload at link add time
>
> ip/ipmacsec.c | 23 ++++++++++++++++++++++-
> man/man8/ip-macsec.8 | 10 ++++++++--
> 2 files changed, 30 insertions(+), 3 deletions(-)
>
applied to iproute2-next. Thanks
next prev parent reply other threads:[~2020-04-26 18:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-24 8:38 [PATCH iproute2-next 0/2] macsec: add offloading support Igor Russkikh
2020-04-24 8:38 ` [PATCH iproute2-next 1/2] macsec: add support for MAC offload Igor Russkikh
2020-04-24 8:38 ` [PATCH iproute2-next 2/2] macsec: add support for specifying offload at link add time Igor Russkikh
2020-04-26 18:33 ` David Ahern [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-20 20:18 [PATCH iproute2-next 0/2] macsec: add offloading support Antoine Tenart
2020-01-28 10:36 ` Sabrina Dubroca
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=0a44a226-0890-c856-58dd-b16e8b83c9dc@gmail.com \
--to=dsahern@gmail.com \
--cc=irusskikh@marvell.com \
--cc=mstarovoitov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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