All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lafreniere <peter@n8pjl.ca>
To: linux-crypto@vger.kernel.org
Cc: Peter Lafreniere <peter@n8pjl.ca>,
	x86@kernel.org, jussi.kivilinna@mbnet.fi
Subject: [PATCH 0/3] crypto: x86/twofish-3way - Cleanup and optimize asm
Date: Sun,  5 Feb 2023 22:24:16 -0500	[thread overview]
Message-ID: <cover.1675653010.git.peter@n8pjl.ca> (raw)

1/3 removes the unused xor argument to encode functions. This argument
is deadweight and its removal shaves off a both a few cycles per call as
well as a small amount of lines.

2/3 moves handling for cbc mode decryption to assembly in order to
remove overhead, yielding a ~6% speedup on AMD Zen1.

3/3 makes a minor readability change that doesn't fit well into 2/3.

Peter Lafreniere (3):
  crypto: x86/twofish-3way - Remove unused encode parameter
  crypto: x86/twofish-3way - Perform cbc xor in assembly
  crypto: x86/twofish-3way - Remove unused macro argument

 arch/x86/crypto/twofish-x86_64-asm_64-3way.S | 71 ++++++++++++--------
 arch/x86/crypto/twofish.h                    | 19 ++++--
 arch/x86/crypto/twofish_avx_glue.c           |  5 --
 arch/x86/crypto/twofish_glue_3way.c          | 22 +-----
 4 files changed, 59 insertions(+), 58 deletions(-)

-- 
2.39.1


             reply	other threads:[~2023-02-06  3:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06  3:24 Peter Lafreniere [this message]
2023-02-06  3:31 ` [PATCH 1/3] crypto: x86/twofish-3way - Remove unused encode parameter Peter Lafreniere
2023-02-06  3:31 ` [PATCH 2/3] crypto: x86/twofish-3way - Perform cbc xor in assembly Peter Lafreniere
2023-02-06  3:31 ` [PATCH 3/3] crypto: x86/twofish-3way - Remove unused macro argument Peter Lafreniere
2023-02-14  8:44 ` [PATCH 0/3] crypto: x86/twofish-3way - Cleanup and optimize asm 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=cover.1675653010.git.peter@n8pjl.ca \
    --to=peter@n8pjl.ca \
    --cc=jussi.kivilinna@mbnet.fi \
    --cc=linux-crypto@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.