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: Sun, 4 Dec 2022 10:00:16 +0200 [thread overview]
Message-ID: <Y4xTkImiAiXavCAN@unreal> (raw)
In-Reply-To: <cover.1670005543.git.leonro@nvidia.com>
On Fri, Dec 02, 2022 at 08:41:26PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> The following series extends XFRM core code to handle a new type of IPsec
> offload - packet offload.
<...>
> 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
Hi Steffen,
Like we discussed on v9 of this series, I do prefer to see this code
merged before merge window. It will simplify so much for me, like
UAPI exposure for iproute2 and *swan* forks. The internal API for
our mlx5 refactoring e.t.c.
The code in our regression is all time and it is completely safe for any
non-packet offload devices.
Thanks
next prev parent reply other threads:[~2022-12-04 8:00 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 ` Leon Romanovsky [this message]
2022-12-06 12:47 ` [PATCH xfrm-next v10 0/8] Extend XFRM core to allow packet offload configuration Steffen Klassert
2022-12-06 13:20 ` Leon Romanovsky
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=Y4xTkImiAiXavCAN@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 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.