From: Sabrina Dubroca <sd@queasysnail.net>
To: Leon Romanovsky <leon@kernel.org>
Cc: Antoine Tenart <atenart@kernel.org>,
netdev@vger.kernel.org,
Mark Starovoytov <mstarovoitov@marvell.com>,
Igor Russkikh <irusskikh@marvell.com>
Subject: Re: [PATCH net 0/5] macsec: offload-related fixes
Date: Mon, 24 Oct 2022 10:24:28 +0200 [thread overview]
Message-ID: <Y1ZLvNE3W9Ph+qqJ@hog> (raw)
In-Reply-To: <Y1Ty2LlrdrhVvLYA@unreal>
2022-10-23, 10:52:56 +0300, Leon Romanovsky wrote:
> On Thu, Oct 20, 2022 at 03:54:28PM +0200, Sabrina Dubroca wrote:
> > 2022-10-18, 09:28:08 +0300, Leon Romanovsky wrote:
> > > On Fri, Oct 14, 2022 at 04:03:56PM +0200, Antoine Tenart wrote:
> > > > Quoting Leon Romanovsky (2022-10-14 13:03:57)
> > > > > On Fri, Oct 14, 2022 at 09:43:45AM +0200, Sabrina Dubroca wrote:
> > > > > > 2022-10-14, 09:13:39 +0300, Leon Romanovsky wrote:
> > > > > > > On Thu, Oct 13, 2022 at 04:15:38PM +0200, Sabrina Dubroca wrote:
>
> <...>
>
> > > > - With the revert: IPsec and MACsec can be offloaded to the lower dev.
> > > > Some features might not propagate to the MACsec dev, which won't allow
> > > > some performance optimizations in the MACsec data path.
> > >
> > > My concern is related to this sentence: "it's not possible to offload macsec
> > > to lower devices that also support ipsec offload", because our devices support
> > > both macsec and IPsec offloads at the same time.
> > >
> > > I don't want to see anything (even in commit messages) that assumes that IPsec
> > > offload doesn't exist.
> >
> > I don't understand what you're saying here. Patch #1 from this series
> > is exactly about the macsec device acknowledging that ipsec offload
> > exists. The rest of the patches is strictly macsec stuff and says
> > nothing about ipsec. Can you point out where, in this series, I'm
> > claiming that ipsec offload doesn't exist?
>
> All this conversation is about one sentence, which I cited above - "it's not possible
> to offload macsec to lower devices that also support ipsec offload". From the comments,
> I think that you wanted to say "macsec offload is not working due to performance
> optimization, where IPsec offload feature flag was exposed from lower device." Did I get
> it correctly, now?
Yes. "In the current state" (that I wrote in front of the sentence you
quoted) refers to the changes introduced by commit c850240b6c41. The
details are present in the commit message for patch 1.
Do you object to the revert, if I rephrase the justification, and then
re-add the features that make sense in net-next?
--
Sabrina
next prev parent reply other threads:[~2022-10-24 8:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 14:15 [PATCH net 0/5] macsec: offload-related fixes Sabrina Dubroca
2022-10-13 14:15 ` [PATCH net 1/5] Revert "net: macsec: report real_dev features when HW offloading is enabled" Sabrina Dubroca
2022-10-13 14:15 ` [PATCH net 2/5] macsec: delete new rxsc when offload fails Sabrina Dubroca
2022-10-13 14:15 ` [PATCH net 3/5] macsec: fix secy->n_rx_sc accounting Sabrina Dubroca
2022-10-14 6:16 ` Leon Romanovsky
2022-10-14 7:43 ` Sabrina Dubroca
2022-10-14 11:08 ` Leon Romanovsky
2022-10-13 14:15 ` [PATCH net 4/5] macsec: fix detection of RXSCs when toggling offloading Sabrina Dubroca
2022-10-13 14:15 ` [PATCH net 5/5] macsec: clear encryption keys from the stack after setting up offload Sabrina Dubroca
2022-10-14 6:13 ` [PATCH net 0/5] macsec: offload-related fixes Leon Romanovsky
2022-10-14 7:43 ` Sabrina Dubroca
2022-10-14 11:03 ` Leon Romanovsky
2022-10-14 14:03 ` Antoine Tenart
2022-10-18 6:28 ` Leon Romanovsky
2022-10-20 13:54 ` Sabrina Dubroca
2022-10-23 7:52 ` Leon Romanovsky
2022-10-24 8:24 ` Sabrina Dubroca [this message]
2022-10-24 8:43 ` Leon Romanovsky
2022-10-24 22:05 ` Sabrina Dubroca
2022-10-25 6:55 ` Leon Romanovsky
2022-10-14 14:44 ` 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=Y1ZLvNE3W9Ph+qqJ@hog \
--to=sd@queasysnail.net \
--cc=atenart@kernel.org \
--cc=irusskikh@marvell.com \
--cc=leon@kernel.org \
--cc=mstarovoitov@marvell.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).