From: Simon Horman <horms@kernel.org>
To: Tanmay Jagdale <tanmay@marvell.com>
Cc: davem@davemloft.net, leon@kernel.org,
herbert@gondor.apana.org.au, bbhushan2@marvell.com,
sgoutham@marvell.com, linux-crypto@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 01/15] crypto: octeontx2: Share engine group info with AF driver
Date: Tue, 28 Oct 2025 11:08:24 +0000 [thread overview]
Message-ID: <aQCkKB-0ocnvM8II@horms.kernel.org> (raw)
In-Reply-To: <20251026150916.352061-2-tanmay@marvell.com>
On Sun, Oct 26, 2025 at 08:38:56PM +0530, Tanmay Jagdale wrote:
> From: Bharat Bhushan <bbhushan2@marvell.com>
>
> CPT crypto hardware have multiple engines of different type
> and these engines of a give type are attached to one of the
> engine group. Software will submit ecnap/decap work to these
> engine group. Engine group details are available with CPT
> crypto driver. This is shared with AF driver using mailbox
> message to enable use cases like inline-ipsec etc.
>
> Also, no need to try to delete engine groups if engine group
> initialization fails. Engine groups will never be created
> before engine group initialization.
>
> Signed-off-by: Bharat Bhushan <bbhushan2@marvell.com>
> Signed-off-by: Tanmay Jagdale <tanmay@marvell.com>
Hi Bharat and Tanmay,
I realise that this patch-set already runs to 15 patches.
But the 'Also' part does feel like it belongs in a separate patch.
...
next prev parent reply other threads:[~2025-10-28 11:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-26 15:08 [PATCH net-next v5 00/15] Enable Inbound IPsec offload on Marvell CN10K SoC Tanmay Jagdale
2025-10-26 15:08 ` [PATCH net-next v5 01/15] crypto: octeontx2: Share engine group info with AF driver Tanmay Jagdale
2025-10-28 11:08 ` Simon Horman [this message]
2025-10-29 17:28 ` Tanmay Jagdale
2025-10-26 15:08 ` [PATCH net-next v5 02/15] octeontx2-af: Configure crypto hardware for inline ipsec Tanmay Jagdale
2025-10-26 15:08 ` [PATCH net-next v5 03/15] octeontx2-af: Setup Large Memory Transaction for crypto Tanmay Jagdale
2025-10-26 15:08 ` [PATCH net-next v5 04/15] octeontx2-af: Handle inbound inline ipsec config in AF Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 05/15] octeontx2-af: Add support for CPT second pass Tanmay Jagdale
2025-10-28 11:07 ` Simon Horman
2025-10-29 17:09 ` Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 06/15] octeontx2-af: Add support for SPI to SA index translation Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 07/15] octeontx2-af: Add mbox to alloc/free BPIDs Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 08/15] octeontx2-pf: ipsec: Setup NIX HW resources for inbound flows Tanmay Jagdale
2025-10-28 10:45 ` Simon Horman
2025-10-29 17:06 ` [EXTERNAL] " Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 09/15] octeontx2-pf: ipsec: Allocate Ingress SA table Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 10/15] octeontx2-pf: ipsec: Handle NPA threshold interrupt Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 11/15] octeontx2-pf: ipsec: Initialize ingress IPsec Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 12/15] octeontx2-pf: ipsec: Configure backpressure Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 13/15] octeontx2-pf: ipsec: Process CPT metapackets Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 14/15] octeontx2-pf: ipsec: Manage NPC rules and SPI-to-SA table entries Tanmay Jagdale
2025-10-26 15:09 ` [PATCH net-next v5 15/15] octeontx2-pf: ipsec: Add XFRM state and policy hooks for inbound flows Tanmay Jagdale
2025-10-28 11:39 ` Sabrina Dubroca
2025-10-29 17:36 ` [EXTERNAL] " Tanmay Jagdale
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=aQCkKB-0ocnvM8II@horms.kernel.org \
--to=horms@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=leon@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sgoutham@marvell.com \
--cc=tanmay@marvell.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).