public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leonro@nvidia.com>
To: Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
	"David S . Miller" <davem@davemloft.net>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
	Saeed Mahameed <saeedm@nvidia.com>,
	linux-netdev <netdev@vger.kernel.org>,
	Raed Salem <raeds@nvidia.com>
Subject: Re: [PATCH net-next v1 00/17] Extra IPsec cleanup
Date: Fri, 22 Apr 2022 20:49:26 +0300	[thread overview]
Message-ID: <YmLqpn6v/HIipias@unreal> (raw)
In-Reply-To: <cover.1650363043.git.leonro@nvidia.com>

On Tue, Apr 19, 2022 at 01:13:36PM +0300, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
> 
> Changelog:
> v1:
>  * changed target from mlx5-next to net-next.
>  * Improved commit message in patch #1
>  * Left function names intact, with _accel_ word in it.
> v0: https://lore.kernel.org/all/cover.1649578827.git.leonro@nvidia.com
> 
> --------------------
> After FPGA IPsec removal, we can go further and make sure that flow
> steering logic is aligned to mlx5_core standard together with deep
> cleaning of whole IPsec path.
> 
> Thanks

Hi,

I see that this series is marked as "Awaiting Upstream" in patchworks.
https://patchwork.kernel.org/project/netdevbpf/list/?series=633295&state=*
What does it mean? Can you please apply it directly to the netdev tree?

Thanks

> 
> Leon Romanovsky (17):
>   net/mlx5: Simplify IPsec flow steering init/cleanup functions
>   net/mlx5: Check IPsec TX flow steering namespace in advance
>   net/mlx5: Don't hide fallback to software IPsec in FS code
>   net/mlx5: Reduce useless indirection in IPsec FS add/delete flows
>   net/mlx5: Store IPsec ESN update work in XFRM state
>   net/mlx5: Remove useless validity check
>   net/mlx5: Merge various control path IPsec headers into one file
>   net/mlx5: Remove indirections from esp functions
>   net/mlx5: Simplify HW context interfaces by using SA entry
>   net/mlx5: Clean IPsec FS add/delete rules
>   net/mlx5: Make sure that no dangling IPsec FS pointers exist
>   net/mlx5: Don't advertise IPsec netdev support for non-IPsec device
>   net/mlx5: Simplify IPsec capabilities logic
>   net/mlx5: Remove not-supported ICV length
>   net/mlx5: Cleanup XFRM attributes struct
>   net/mlx5: Allow future addition of IPsec object modifiers
>   net/mlx5: Don't perform lookup after already known sec_path
> 
>  .../net/ethernet/mellanox/mlx5/core/en/fs.h   |   1 -
>  .../ethernet/mellanox/mlx5/core/en/params.c   |   2 +-
>  .../mellanox/mlx5/core/en_accel/ipsec.c       | 174 +++------
>  .../mellanox/mlx5/core/en_accel/ipsec.h       |  85 +++-
>  .../mellanox/mlx5/core/en_accel/ipsec_fs.c    | 362 ++++++------------
>  .../mellanox/mlx5/core/en_accel/ipsec_fs.h    |   4 +-
>  .../mlx5/core/en_accel/ipsec_offload.c        | 331 +++-------------
>  .../mlx5/core/en_accel/ipsec_offload.h        |  14 -
>  .../mellanox/mlx5/core/en_accel/ipsec_rxtx.c  |   6 +-
>  .../mellanox/mlx5/core/en_accel/ipsec_stats.c |   4 +-
>  .../net/ethernet/mellanox/mlx5/core/en_main.c |   1 -
>  .../net/ethernet/mellanox/mlx5/core/en_rx.c   |   2 +-
>  .../net/ethernet/mellanox/mlx5/core/main.c    |   2 +-
>  include/linux/mlx5/accel.h                    | 153 --------
>  include/linux/mlx5/mlx5_ifc.h                 |   2 -
>  15 files changed, 320 insertions(+), 823 deletions(-)
>  delete mode 100644 drivers/net/ethernet/mellanox/mlx5/core/en_accel/ipsec_offload.h
>  delete mode 100644 include/linux/mlx5/accel.h
> 
> -- 
> 2.35.1
> 

  parent reply	other threads:[~2022-04-22 18:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 10:13 [PATCH net-next v1 00/17] Extra IPsec cleanup Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 01/17] net/mlx5: Simplify IPsec flow steering init/cleanup functions Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 02/17] net/mlx5: Check IPsec TX flow steering namespace in advance Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 03/17] net/mlx5: Don't hide fallback to software IPsec in FS code Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 04/17] net/mlx5: Reduce useless indirection in IPsec FS add/delete flows Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 05/17] net/mlx5: Store IPsec ESN update work in XFRM state Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 06/17] net/mlx5: Remove useless validity check Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 07/17] net/mlx5: Merge various control path IPsec headers into one file Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 08/17] net/mlx5: Remove indirections from esp functions Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 09/17] net/mlx5: Simplify HW context interfaces by using SA entry Leon Romanovsky
2022-04-22 22:19   ` Saeed Mahameed
2022-05-01  8:56     ` Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 10/17] net/mlx5: Clean IPsec FS add/delete rules Leon Romanovsky
2022-04-22 22:25   ` Saeed Mahameed
2022-05-01  8:52     ` Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 11/17] net/mlx5: Make sure that no dangling IPsec FS pointers exist Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 12/17] net/mlx5: Don't advertise IPsec netdev support for non-IPsec device Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 13/17] net/mlx5: Simplify IPsec capabilities logic Leon Romanovsky
2022-04-22 22:42   ` Saeed Mahameed
2022-05-01  8:42     ` Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 14/17] net/mlx5: Remove not-supported ICV length Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 15/17] net/mlx5: Cleanup XFRM attributes struct Leon Romanovsky
2022-04-22 22:45   ` Saeed Mahameed
2022-05-01  8:05     ` Leon Romanovsky
2022-04-19 10:13 ` [PATCH net-next v1 16/17] net/mlx5: Allow future addition of IPsec object modifiers Leon Romanovsky
2022-04-22 22:46   ` Saeed Mahameed
2022-04-19 10:13 ` [PATCH net-next v1 17/17] net/mlx5: Don't perform lookup after already known sec_path Leon Romanovsky
2022-04-22 17:49 ` Leon Romanovsky [this message]
2022-04-22 17:55   ` [PATCH net-next v1 00/17] Extra IPsec cleanup Saeed Mahameed

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=YmLqpn6v/HIipias@unreal \
    --to=leonro@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=jgg@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=raeds@nvidia.com \
    --cc=saeedm@nvidia.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