All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
	"Chang S . Bae" <chang.seok.bae@intel.com>
Subject: [PATCH 0/3] crypto: x86/aes-xts - additional tuning
Date: Fri, 12 Apr 2024 20:17:25 -0700	[thread overview]
Message-ID: <20240413031728.159495-1-ebiggers@kernel.org> (raw)

This series does some more fine-tuning of the new AES-XTS code.

It applies to cryptodev commit 751fb2528c12 plus the two pending patches
https://lore.kernel.org/linux-crypto/20240409000154.29799-1-ebiggers@kernel.org/
and
https://lore.kernel.org/linux-crypto/20240412154559.91807-1-ebiggers@kernel.org/

Eric Biggers (3):
  crypto: x86/aes-xts - handle AES-128 and AES-192 more efficiently
  crypto: x86/aes-xts - eliminate a few more instructions
  crypto: x86/aes-xts - optimize size of instructions operating on
    lengths

 arch/x86/crypto/aes-xts-avx-x86_64.S | 249 +++++++++++++--------------
 arch/x86/crypto/aesni-intel_glue.c   |  18 +-
 2 files changed, 131 insertions(+), 136 deletions(-)


base-commit: 751fb2528c12ef64d1e863efb196cdc968b384f6
prerequisite-patch-id: 5c1ca8ffe87136eb7bfe74d996f5e6cac01e2768
prerequisite-patch-id: a72a872736c8e0876c4b44a9e5792dcaa02d4e0e
-- 
2.44.0


             reply	other threads:[~2024-04-13  3:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-13  3:17 Eric Biggers [this message]
2024-04-13  3:17 ` [PATCH 1/3] crypto: x86/aes-xts - handle AES-128 and AES-192 more efficiently Eric Biggers
2024-04-13  3:17 ` [PATCH 2/3] crypto: x86/aes-xts - eliminate a few more instructions Eric Biggers
2024-04-13  3:17 ` [PATCH 3/3] crypto: x86/aes-xts - optimize size of instructions operating on lengths Eric Biggers
2024-04-15 12:11 ` [PATCH 0/3] crypto: x86/aes-xts - additional tuning Ard Biesheuvel
2024-04-19 11:04 ` 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=20240413031728.159495-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=chang.seok.bae@intel.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.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 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.