All of lore.kernel.org
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
	fsverity@lists.linux.dev, dm-devel@lists.linux.dev,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	Ard Biesheuvel <ardb@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Megha Dey <megha.dey@linux.intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: [PATCH v4 6/8] fsverity: improve performance by using multibuffer hashing
Date: Thu, 6 Jun 2024 13:41:12 +0800	[thread overview]
Message-ID: <ZmFL-AXZ8lphOCUC@gondor.apana.org.au> (raw)
In-Reply-To: <20240606052801.GA324380@sol.localdomain>

On Wed, Jun 05, 2024 at 10:28:01PM -0700, Eric Biggers wrote:
>
> With AES, interleaving would only help with non-parallelizable modes such as CBC
> encryption.  Anyone who cares about IPsec performance should of course be using
> AES-GCM, which is parallelizable.  Especially since my other patch
> https://lore.kernel.org/linux-crypto/20240602222221.176625-2-ebiggers@kernel.org/
> is making AES-GCM twice as fast...

Algorithm selection may be limited by peer capability.  For IPsec,
if SHA is being used, then most likely CBC is also being used.

> In any case, it seems that what you're asking for at this point is far beyond
> the scope of this patchset.

I'm more than happy to take this over if you don't wish to extend
it beyond the storage usage cases.  According to the original Intel
sha2-mb submission, this should result in at least a two-fold
speed-up.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

WARNING: multiple messages have this Message-ID (diff)
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
	netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
	fsverity@lists.linux.dev, dm-devel@lists.linux.dev,
	x86@kernel.org, linux-arm-kernel@lists.infradead.org,
	Ard Biesheuvel <ardb@kernel.org>,
	Sami Tolvanen <samitolvanen@google.com>,
	Bart Van Assche <bvanassche@acm.org>,
	Megha Dey <megha.dey@linux.intel.com>,
	Tim Chen <tim.c.chen@linux.intel.com>
Subject: Re: [PATCH v4 6/8] fsverity: improve performance by using multibuffer hashing
Date: Thu, 6 Jun 2024 13:41:12 +0800	[thread overview]
Message-ID: <ZmFL-AXZ8lphOCUC@gondor.apana.org.au> (raw)
In-Reply-To: <20240606052801.GA324380@sol.localdomain>

On Wed, Jun 05, 2024 at 10:28:01PM -0700, Eric Biggers wrote:
>
> With AES, interleaving would only help with non-parallelizable modes such as CBC
> encryption.  Anyone who cares about IPsec performance should of course be using
> AES-GCM, which is parallelizable.  Especially since my other patch
> https://lore.kernel.org/linux-crypto/20240602222221.176625-2-ebiggers@kernel.org/
> is making AES-GCM twice as fast...

Algorithm selection may be limited by peer capability.  For IPsec,
if SHA is being used, then most likely CBC is also being used.

> In any case, it seems that what you're asking for at this point is far beyond
> the scope of this patchset.

I'm more than happy to take this over if you don't wish to extend
it beyond the storage usage cases.  According to the original Intel
sha2-mb submission, this should result in at least a two-fold
speed-up.

Cheers,
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-06-06  5:41 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 18:37 [PATCH v4 0/8] Optimize dm-verity and fsverity using multibuffer hashing Eric Biggers
2024-06-03 18:37 ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 1/8] crypto: shash - add support for finup_mb Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-04 18:55   ` Ard Biesheuvel
2024-06-04 18:55     ` Ard Biesheuvel
2024-06-04 19:25     ` Eric Biggers
2024-06-04 19:25       ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 2/8] crypto: testmgr - generate power-of-2 lengths more often Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 3/8] crypto: testmgr - add tests for finup_mb Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 4/8] crypto: x86/sha256-ni - add support " Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 5/8] crypto: arm64/sha256-ce " Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-04 19:00   ` Ard Biesheuvel
2024-06-04 19:00     ` Ard Biesheuvel
2024-06-03 18:37 ` [PATCH v4 6/8] fsverity: improve performance by using multibuffer hashing Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-04  9:37   ` Herbert Xu
2024-06-04  9:37     ` Herbert Xu
2024-06-04 18:42     ` Eric Biggers
2024-06-04 18:42       ` Eric Biggers
2024-06-05  9:19       ` Herbert Xu
2024-06-05  9:19         ` Herbert Xu
2024-06-05  9:22         ` Herbert Xu
2024-06-05  9:22           ` Herbert Xu
2024-06-05  9:46           ` Herbert Xu
2024-06-05  9:46             ` Herbert Xu
2024-06-05 19:14             ` Eric Biggers
2024-06-05 19:14               ` Eric Biggers
2024-06-06  2:00               ` Herbert Xu
2024-06-06  2:00                 ` Herbert Xu
2024-06-06  5:28                 ` Eric Biggers
2024-06-06  5:28                   ` Eric Biggers
2024-06-06  5:41                   ` Herbert Xu [this message]
2024-06-06  5:41                     ` Herbert Xu
2024-06-06  6:58                     ` Ard Biesheuvel
2024-06-06  6:58                       ` Ard Biesheuvel
2024-06-06  7:34                       ` Herbert Xu
2024-06-06  7:34                         ` Herbert Xu
2024-06-06  7:55                         ` Ard Biesheuvel
2024-06-06  7:55                           ` Ard Biesheuvel
2024-06-06  8:08                           ` Herbert Xu
2024-06-06  8:08                             ` Herbert Xu
2024-06-06  8:33                             ` Ard Biesheuvel
2024-06-06  8:33                               ` Ard Biesheuvel
2024-06-06  9:15                               ` Herbert Xu
2024-06-06  9:15                                 ` Herbert Xu
2024-06-10 16:42                                 ` Eric Biggers
2024-06-10 16:42                                   ` Eric Biggers
2024-06-11 15:21                                   ` Herbert Xu
2024-06-11 15:21                                     ` Herbert Xu
2024-06-11 15:39                                     ` Herbert Xu
2024-06-11 15:39                                       ` Herbert Xu
2024-06-11 20:32                                       ` Eric Biggers
2024-06-11 15:46                                     ` Ard Biesheuvel
2024-06-11 15:46                                       ` Ard Biesheuvel
2024-06-11 15:51                                       ` Herbert Xu
2024-06-11 15:51                                         ` Herbert Xu
2024-06-11 20:18                                     ` Eric Biggers
2024-06-05 18:58         ` Eric Biggers
2024-06-05 18:58           ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 7/8] dm-verity: hash blocks with shash import+finup when possible Eric Biggers
2024-06-03 18:37   ` Eric Biggers
2024-06-03 18:37 ` [PATCH v4 8/8] dm-verity: improve performance by using multibuffer hashing Eric Biggers
2024-06-03 18:37   ` Eric Biggers

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=ZmFL-AXZ8lphOCUC@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=ardb@kernel.org \
    --cc=bvanassche@acm.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=ebiggers@kernel.org \
    --cc=fsverity@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=megha.dey@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=samitolvanen@google.com \
    --cc=steffen.klassert@secunet.com \
    --cc=tim.c.chen@linux.intel.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.