From: David Laight <david.laight.linux@gmail.com>
To: Simon Richter <Simon.Richter@hogyros.de>
Cc: Eric Biggers <ebiggers@kernel.org>,
Hendrik Donner <hd@os-cillation.de>,
linux-crypto@vger.kernel.org,
Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>,
Thomas Huth <thuth@redhat.com>
Subject: Re: [PATCH 1/2] crypto: pcrypt - Remove pcrypt
Date: Thu, 23 Jul 2026 09:01:13 +0100 [thread overview]
Message-ID: <20260723090113.5c2b9995@pumpkin> (raw)
In-Reply-To: <d45ed4a1-da22-44a3-9f9e-78041dd338b1@hogyros.de>
On Thu, 23 Jul 2026 08:30:47 +0900
Simon Richter <Simon.Richter@hogyros.de> wrote:
> Hi,
>
> On 7/23/26 4:40 AM, Eric Biggers wrote:
>
> > So while maybe pcrypt does still help a bit on this platform for now,
> > the approach does seem quite dated and largely a workaround for
> > inefficiencies elsewhere in the stack (including systems where the
> > optimized crypto code is accidentally not enabled).
>
> There is one additional aspect: offloading frees the CPU to do something
> else -- and that is where even offload engines that are slower than the
> CPU can still be beneficial in the big picture.
Provided what is being offload actually takes long enough to allow for
setting up the iommu, the two context switches and the interrupt as well as
the obvious setup costs.
David
>
> Simon
>
next prev parent reply other threads:[~2026-07-23 8:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 22:32 [PATCH 0/2] Remove pcrypt Eric Biggers
2026-07-13 22:32 ` [PATCH 1/2] crypto: pcrypt - " Eric Biggers
2026-07-14 4:20 ` Thomas Huth
2026-07-21 18:59 ` Hendrik Donner
2026-07-21 19:50 ` Eric Biggers
2026-07-22 16:12 ` Hendrik Donner
2026-07-22 19:40 ` Eric Biggers
2026-07-22 23:30 ` Simon Richter
2026-07-23 8:01 ` David Laight [this message]
2026-07-13 22:32 ` [PATCH 2/2] padata: Remove serialized job support Eric Biggers
2026-07-14 4:28 ` Thomas Huth
2026-07-17 20:32 ` Daniel Jordan
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=20260723090113.5c2b9995@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=Simon.Richter@hogyros.de \
--cc=ebiggers@kernel.org \
--cc=hd@os-cillation.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=thuth@redhat.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