From: Christoph Hellwig <hch@infradead.org>
To: Leonid Ravich <lravich@amazon.com>
Cc: linux-crypto@vger.kernel.org, dm-devel@lists.linux.dev,
herbert@gondor.apana.org.au, davem@davemloft.net,
ebiggers@kernel.org, agk@redhat.com, snitzer@kernel.org,
mpatocka@redhat.com, bmarzins@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 0/6] crypto: skcipher - multi-data-unit request splitting
Date: Fri, 25 Sep 2026 02:10:47 -0700 [thread overview]
Message-ID: <arY6lzQtvVzUGngU@infradead.org> (raw)
In-Reply-To: <20260924075846.28203-1-lravich@amazon.com>
On Thu, Sep 24, 2026 at 07:58:40AM +0000, Leonid Ravich wrote:
> * No throughput *win* is claimed for software AES. The win is for
> accelerators that amortise setup across units; the software split
> exists so the interface works on every existing skcipher today and
> goes quiet as algorithms gain CRYPTO_ALG_REQ_SEG.
So what is the use case? So far all crypto driver we've seen have
shown to be slower than cpu. Which one are you using that isn't?
And if you have a genuinely useful one, should we have a proper
interface to it that doesn't pay the scatterlist overhead to start
with?
prev parent reply other threads:[~2026-09-25 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:58 Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 1/6] crypto: skcipher - add per-request unit_size Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 2/6] crypto: acomp - Add bit to indicate segmentation support Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 3/6] crypto: skcipher - add crypto_skcipher_req_seg() helper Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 4/6] crypto: skcipher - split multi-unit requests in the API layer Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 5/6] crypto: testmgr - test multi-unit dispatch Leonid Ravich
2026-09-24 7:58 ` [PATCH v6 6/6] dm crypt: batch a bio segment's sectors via multi-unit requests Leonid Ravich
2026-09-25 9:10 ` Christoph Hellwig [this message]
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=arY6lzQtvVzUGngU@infradead.org \
--to=hch@infradead.org \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=davem@davemloft.net \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lravich@amazon.com \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.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
all inboxes | Powered by JetHome®