From: Horia Geanta <horia.geanta@nxp.com>
To: Ovidiu Panait <ovidiu.panait.oss@gmail.com>,
"herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "freude@linux.ibm.com" <freude@linux.ibm.com>,
"dengler@linux.ibm.com" <dengler@linux.ibm.com>,
"linux-s390@vger.kernel.org" <linux-s390@vger.kernel.org>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
Gaurav Jain <gaurav.jain@nxp.com>,
"arei.gonglei@huawei.com" <arei.gonglei@huawei.com>,
"virtualization@lists.linux.dev" <virtualization@lists.linux.dev>
Subject: Re: [PATCH 1/2] crypto: engine: remove request batching support
Date: Tue, 15 Jul 2025 21:38:32 +0000 [thread overview]
Message-ID: <701ab192-9c96-43b8-805e-a8e9953f7abc@nxp.com> (raw)
In-Reply-To: <20250711182932.918257-1-ovidiu.panait.oss@gmail.com>
On 7/11/2025 9:30 PM, Ovidiu Panait wrote:
> Remove request batching support from crypto_engine, as there are no
> drivers using this feature and it doesn't really work that well.
>
> Instead of doing batching based on backlog, a more optimal approach
> would be for the user to handle the batching (similar to how IPsec
> can hook into GSO to get 64K of data each time or how block encryption
> can use unit sizes much greater than 4K).
>
> Suggested-by: Herbert Xu <herbert@gondor.apana.org.au>
> Signed-off-by: Ovidiu Panait <ovidiu.panait.oss@gmail.com>
Reviewed-by: Horia Geantă <horia.geanta@nxp.com>
Thanks,
Horia
next prev parent reply other threads:[~2025-07-15 21:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-11 18:29 Ovidiu Panait
2025-07-11 18:29 ` [PATCH 2/2] crypto: engine: remove {prepare,unprepare}_crypt_hardware callbacks Ovidiu Panait
2025-07-15 21:38 ` Horia Geanta [this message]
2025-07-18 11:13 ` [PATCH 1/2] crypto: engine: remove request batching support Herbert Xu
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=701ab192-9c96-43b8-805e-a8e9953f7abc@nxp.com \
--to=horia.geanta@nxp.com \
--cc=arei.gonglei@huawei.com \
--cc=davem@davemloft.net \
--cc=dengler@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=ovidiu.panait.oss@gmail.com \
--cc=pankaj.gupta@nxp.com \
--cc=virtualization@lists.linux.dev \
/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
all inboxes | Powered by JetHome®