linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-crypto@vger.kernel.org
Subject: [PATCH 0/2] crypto: api - remove crypto_tfm::crt_u
Date: Mon,  2 Dec 2019 13:42:28 -0800	[thread overview]
Message-ID: <20191202214230.164997-1-ebiggers@kernel.org> (raw)

This series removes the per-algorithm-type union from struct crypto_tfm
now that its only remaining users are the "compress" and "cipher"
algorithm types, and it's not really needed for them.

This shrinks every crypto transform for every algorithm by 28 bytes on
64-bit platforms (12 bytes on 32-bit), and also removes some code.

Note that the new-style strongly-typed algorithms (i.e. everything other
than "compress" and "cipher") don't need crt_u, since they embed struct
crypto_tfm in a per-algorithm-type custom struct instead.

Eric Biggers (2):
  crypto: compress - remove crt_u.compress (struct compress_tfm)
  crypto: cipher - remove crt_u.cipher (struct cipher_tfm)

 crypto/api.c           | 15 +------
 crypto/cipher.c        | 92 +++++++++++++++++-------------------------
 crypto/compress.c      | 31 ++++++--------
 crypto/internal.h      |  3 --
 include/linux/crypto.h | 91 ++++++-----------------------------------
 5 files changed, 61 insertions(+), 171 deletions(-)

-- 
2.24.0.393.g34dc348eaf-goog


             reply	other threads:[~2019-12-02 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-02 21:42 Eric Biggers [this message]
2019-12-02 21:42 ` [PATCH 1/2] crypto: compress - remove crt_u.compress (struct compress_tfm) Eric Biggers
2019-12-02 21:42 ` [PATCH 2/2] crypto: cipher - remove crt_u.cipher (struct cipher_tfm) Eric Biggers
2019-12-03 11:42 ` [PATCH 0/2] crypto: api - remove crypto_tfm::crt_u Ard Biesheuvel
2019-12-11  9:43 ` 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=20191202214230.164997-1-ebiggers@kernel.org \
    --to=ebiggers@kernel.org \
    --cc=linux-crypto@vger.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 NNTP newsgroup(s).