From: Leon Romanovsky <leon@kernel.org>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, Bharat Bhushan <bbhushan2@marvell.com>
Subject: Re: [PATCH xfrm-next v10 0/8] Extend XFRM core to allow packet offload configuration
Date: Tue, 6 Dec 2022 15:20:55 +0200 [thread overview]
Message-ID: <Y49Bt6hbfvA7rKem@unreal> (raw)
In-Reply-To: <20221206124745.GH704954@gauss3.secunet.de>
On Tue, Dec 06, 2022 at 01:47:45PM +0100, Steffen Klassert wrote:
> On Fri, Dec 02, 2022 at 08:41:26PM +0200, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> ...
> >
> > Leon Romanovsky (8):
> > xfrm: add new packet offload flag
> > xfrm: allow state packet offload mode
> > xfrm: add an interface to offload policy
> > xfrm: add TX datapath support for IPsec packet offload mode
> > xfrm: add RX datapath protection for IPsec packet offload mode
> > xfrm: speed-up lookup of HW policies
> > xfrm: add support to HW update soft and hard limits
> > xfrm: document IPsec packet offload mode
> >
> > Documentation/networking/xfrm_device.rst | 62 +++++-
> > .../inline_crypto/ch_ipsec/chcr_ipsec.c | 4 +
> > .../net/ethernet/intel/ixgbe/ixgbe_ipsec.c | 5 +
> > drivers/net/ethernet/intel/ixgbevf/ipsec.c | 5 +
> > .../mellanox/mlx5/core/en_accel/ipsec.c | 4 +
> > .../net/ethernet/netronome/nfp/crypto/ipsec.c | 5 +
> > drivers/net/netdevsim/ipsec.c | 5 +
> > include/linux/netdevice.h | 4 +
> > include/net/xfrm.h | 124 +++++++++---
> > include/uapi/linux/xfrm.h | 6 +
> > net/xfrm/xfrm_device.c | 109 +++++++++-
> > net/xfrm/xfrm_output.c | 12 +-
> > net/xfrm/xfrm_policy.c | 85 +++++++-
> > net/xfrm/xfrm_state.c | 191 ++++++++++++++++--
> > net/xfrm/xfrm_user.c | 20 ++
> > 15 files changed, 577 insertions(+), 64 deletions(-)
>
> Series applied, thanks a lot Leon!
Thanks a lot for your help.
prev parent reply other threads:[~2022-12-06 13:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:41 [PATCH xfrm-next v10 0/8] Extend XFRM core to allow packet offload configuration Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 1/8] xfrm: add new packet offload flag Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 2/8] xfrm: allow state packet offload mode Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 3/8] xfrm: add an interface to offload policy Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 4/8] xfrm: add TX datapath support for IPsec packet offload mode Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 5/8] xfrm: add RX datapath protection " Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 6/8] xfrm: speed-up lookup of HW policies Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 7/8] xfrm: add support to HW update soft and hard limits Leon Romanovsky
2022-12-02 18:41 ` [PATCH xfrm-next v10 8/8] xfrm: document IPsec packet offload mode Leon Romanovsky
2022-12-04 8:00 ` [PATCH xfrm-next v10 0/8] Extend XFRM core to allow packet offload configuration Leon Romanovsky
2022-12-06 12:47 ` Steffen Klassert
2022-12-06 13:20 ` Leon Romanovsky [this message]
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=Y49Bt6hbfvA7rKem@unreal \
--to=leon@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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