Linux-Crypto Archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-crypto@vger.kernel.org, x86@kernel.org,
	linux-kernel@vger.kernel.org, ardb@kernel.org, luto@kernel.org,
	chang.seok.bae@intel.com
Subject: Re: [PATCH] crypto: x86/aes-xts - make non-AVX implementation use new glue code
Date: Fri, 12 Apr 2024 15:34:15 +0800	[thread overview]
Message-ID: <Zhjj97HevVmll+gz@gondor.apana.org.au> (raw)
In-Reply-To: <20240407212231.41781-1-ebiggers@kernel.org>

Eric Biggers <ebiggers@kernel.org> wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> Make the non-AVX implementation of AES-XTS (xts-aes-aesni) use the new
> glue code that was introduced for the AVX implementations of AES-XTS.
> This reduces code size, and it improves the performance of xts-aes-aesni
> due to the optimization for messages that don't span page boundaries.
> 
> This required moving the new glue functions higher up in the file and
> allowing the IV encryption function to be specified by the caller.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
> arch/x86/crypto/aes-xts-avx-x86_64.S |   2 +-
> arch/x86/crypto/aesni-intel_asm.S    |  16 +-
> arch/x86/crypto/aesni-intel_glue.c   | 317 +++++++++++----------------
> 3 files changed, 132 insertions(+), 203 deletions(-)

Patch applied.  Thanks.
-- 
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

      reply	other threads:[~2024-04-12  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 21:22 [PATCH] crypto: x86/aes-xts - make non-AVX implementation use new glue code Eric Biggers
2024-04-12  7:34 ` Herbert Xu [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=Zhjj97HevVmll+gz@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=ardb@kernel.org \
    --cc=chang.seok.bae@intel.com \
    --cc=ebiggers@kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).