[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
<IA2PR18MB5885505093B8624E20DDC799D6FAA@IA2PR18MB5885.namprd18.prod.outlook.com>
Date: Wed, 29 Oct 2025 17:28:32 +0000
From: Tanmay Jagdale <tanmay@...vell.com>
To: Simon Horman <horms@...nel.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"leon@...nel.org"
<leon@...nel.org>,
"herbert@...dor.apana.org.au"
<herbert@...dor.apana.org.au>,
Bharat Bhushan <bbhushan2@...vell.com>,
Sunil
Kovvuri Goutham <sgoutham@...vell.com>,
"linux-crypto@...r.kernel.org"
<linux-crypto@...r.kernel.org>,
"netdev@...r.kernel.org"
<netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v5 01/15] crypto: octeontx2: Share engine group
info with AF driver
HI Simon,
>> From: Bharat Bhushan <bbhushan2@...vell.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@...vell.com>
>> Signed-off-by: Tanmay Jagdale <tanmay@...vell.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.
Okay sure. I will think of a way to split this patch and keep the
patch count at 15.
With Regards,
Tanmay
...
Powered by blists - more mailing lists