From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: Louis Peens <louis.peens@corigine.com>,
David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Simon Horman <simon.horman@corigine.com>,
Shihong Wang <shihong.wang@corigine.com>,
netdev@vger.kernel.org, oss-drivers@corigine.com
Subject: Re: [PATCH net-next 1/2] xfrm: add the description of CHACHA20-POLY1305 for xfrm algorithm description
Date: Wed, 19 Jul 2023 13:02:22 +0300 [thread overview]
Message-ID: <20230719100222.GL8808@unreal> (raw)
In-Reply-To: <ZLeyLedVE2pwGEnK@gauss3.secunet.de>
On Wed, Jul 19, 2023 at 11:51:41AM +0200, Steffen Klassert wrote:
> On Wed, Jul 19, 2023 at 12:35:09PM +0300, Leon Romanovsky wrote:
> > On Wed, Jul 19, 2023 at 11:27:27AM +0200, Steffen Klassert wrote:
> > > On Wed, Jul 19, 2023 at 11:18:29AM +0200, Louis Peens wrote:
> > > > From: Shihong Wang <shihong.wang@corigine.com>
> > > >
> > > > Add the description of CHACHA20-POLY1305 for xfrm algorithm description
> > > > and set pfkey_supported to 1 so that xfrm supports that the algorithm
> > > > can be offloaded to the NIC.
> > > >
> > > > Signed-off-by: Shihong Wang <shihong.wang@corigine.com>
> > > > Acked-by: Simon Horman <simon.horman@corigine.com>
> > > > Signed-off-by: Louis Peens <louis.peens@corigine.com>
> > > > ---
> > > > include/uapi/linux/pfkeyv2.h | 1 +
> > > > net/xfrm/xfrm_algo.c | 9 ++++++++-
> > > > 2 files changed, 9 insertions(+), 1 deletion(-)
> > > >
> > > > diff --git a/include/uapi/linux/pfkeyv2.h b/include/uapi/linux/pfkeyv2.h
> > > > index 8abae1f6749c..d0ab530e1069 100644
> > > > --- a/include/uapi/linux/pfkeyv2.h
> > > > +++ b/include/uapi/linux/pfkeyv2.h
> > > > @@ -331,6 +331,7 @@ struct sadb_x_filter {
> > > > #define SADB_X_EALG_CAMELLIACBC 22
> > > > #define SADB_X_EALG_NULL_AES_GMAC 23
> > > > #define SADB_X_EALG_SM4CBC 24
> > > > +#define SADB_X_EALG_CHACHA20_POLY1305 25
> > >
> > > Please don't add new stuff to pfkey, use netlink instead. This interface
> > > is deprecated and will go away someday
> >
> > Steffen, I have general questions.
> > >From where did all these SADB_X_EALG_* values come?
> > And there are they used?
>
> The pfkey interface was used by the old ipsec tools:
> https://ipsec-tools.sourceforge.net/
>
> The development of ipsec-tools has been abandoned
> in 2014, as you can see at the webpage.
Thanks
next prev parent reply other threads:[~2023-07-19 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 9:18 [PATCH net-next 0/2] net: add offload support for CHACHA20-POLY1305 Louis Peens
2023-07-19 9:18 ` [PATCH net-next 1/2] xfrm: add the description of CHACHA20-POLY1305 for xfrm algorithm description Louis Peens
2023-07-19 9:27 ` Steffen Klassert
2023-07-19 9:35 ` Leon Romanovsky
2023-07-19 9:51 ` Steffen Klassert
2023-07-19 10:02 ` Leon Romanovsky [this message]
2023-07-19 10:52 ` Yinjun Zhang
2023-07-19 11:10 ` Steffen Klassert
2023-07-19 9:18 ` [PATCH net-next 2/2] nfp: add support CHACHA20-POLY1305 offload for ipsec Louis Peens
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=20230719100222.GL8808@unreal \
--to=leon@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=louis.peens@corigine.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=shihong.wang@corigine.com \
--cc=simon.horman@corigine.com \
--cc=steffen.klassert@secunet.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).