linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Corentin Labbe <clabbe.montjoie@gmail.com>
To: Ovidiu Panait <ovidiu.panait.oss@gmail.com>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
	linux-crypto@vger.kernel.org, wens@csie.org,
	jernej.skrabec@gmail.com, samuel@sholland.org,
	linux-arm-kernel@lists.infradead.org,
	linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 00/10] crypto: sun8i-ce - implement request batching
Date: Sun, 29 Jun 2025 20:37:33 +0200	[thread overview]
Message-ID: <aGGH7RH8-yHVVz25@Red> (raw)
In-Reply-To: <20250626095813.83963-1-ovidiu.panait.oss@gmail.com>

Le Thu, Jun 26, 2025 at 12:58:03PM +0300, Ovidiu Panait a écrit :
> The Allwinner crypto engine can process multiple requests at a time,
> if they are chained together using the task descriptor's 'next' field.
> Having multiple requests processed in one go can reduce the number
> of interrupts generated and also improve throughput.
> 
> When compared to the existing non-batching implementation, the tcrypt
> multibuffer benchmark shows an increase in throughput of ~85% for 16 byte
> AES blocks (when testing with 8 data streams on the OrangePi Zero2 board).
> 
> Patches 1-9 perform refactoring work on the existing do_one_request()
> callbacks, to make them more modular and easier to integrate with the
> request batching workflow.
> 
> Patch 10 implements the actual request batching.
> 
> Changes in v2:
>    - fixed [-Wformat-truncation=] warning reported by kernel test robot
> 

Hello

Thanks for your patch, I am starting review and test it.

@Herbert, please me give me time for it.

Regards


  parent reply	other threads:[~2025-06-29 18:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  9:58 [PATCH v2 00/10] crypto: sun8i-ce - implement request batching Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 01/10] crypto: sun8i-ce - remove channel timeout field Ovidiu Panait
2025-07-08 12:58   ` Corentin Labbe
2025-06-26  9:58 ` [PATCH v2 02/10] crypto: sun8i-ce - remove boilerplate in sun8i_ce_hash_digest() Ovidiu Panait
2025-07-08 14:04   ` Corentin Labbe
2025-06-26  9:58 ` [PATCH v2 03/10] crypto: sun8i-ce - move bounce_iv and backup_iv to request context Ovidiu Panait
2025-07-08 18:36   ` Corentin Labbe
2025-07-08 20:08     ` Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 04/10] crypto: sun8i-ce - save hash buffers and dma info " Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 05/10] crytpo: sun8i-ce - factor out prepare/unprepare code from ahash do_one_request Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 06/10] crypto: sun8i-ce - fold sun8i_ce_cipher_run() into sun8i_ce_cipher_do_one() Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 07/10] crypto: sun8i-ce - pass task descriptor to cipher prepare/unprepare Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 08/10] crypto: sun8i-ce - factor out public versions of finalize request Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 09/10] crypto: sun8i-ce - add a new function for dumping task descriptors Ovidiu Panait
2025-06-26  9:58 ` [PATCH v2 10/10] crypto: sun8i-ce - implement request batching Ovidiu Panait
2025-06-29 18:37 ` Corentin Labbe [this message]
2025-07-10  8:12 ` [PATCH v2 00/10] " 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=aGGH7RH8-yHVVz25@Red \
    --to=clabbe.montjoie@gmail.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=jernej.skrabec@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=ovidiu.panait.oss@gmail.com \
    --cc=samuel@sholland.org \
    --cc=wens@csie.org \
    /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).