LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Michael Ellerman <mpe@ellerman.id.au> To: herbert@gondor.apana.org.au Cc: linux-crypto@vger.kernel.org, linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org, mhcerri@linux.vnet.ibm.com, pfsmorigo@linux.vnet.ibm.com Subject: [PATCH 2/2] crypto: vmx - Remove overly verbose printk from AES XTS init Date: Thu, 3 May 2018 22:29:30 +1000 [thread overview] Message-ID: <20180503122930.17448-2-mpe@ellerman.id.au> (raw) In-Reply-To: <20180503122930.17448-1-mpe@ellerman.id.au> In p8_aes_xts_init() we do a printk(KERN_INFO ...) to report the fallback implementation we're using. However with a slow console this can significantly affect the speed of crypto operations. So remove it. Fixes: c07f5d3da643 ("crypto: vmx - Adding support for XTS") Cc: stable@vger.kernel.org # v4.8+ Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> --- drivers/crypto/vmx/aes_xts.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/crypto/vmx/aes_xts.c b/drivers/crypto/vmx/aes_xts.c index 8cd6e62e4c90..8bd9aff0f55f 100644 --- a/drivers/crypto/vmx/aes_xts.c +++ b/drivers/crypto/vmx/aes_xts.c @@ -53,8 +53,6 @@ static int p8_aes_xts_init(struct crypto_tfm *tfm) alg, PTR_ERR(fallback)); return PTR_ERR(fallback); } - printk(KERN_INFO "Using '%s' as fallback implementation.\n", - crypto_skcipher_driver_name(fallback)); crypto_skcipher_set_flags( fallback, -- 2.14.1
next prev parent reply other threads:[~2018-05-03 12:29 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-05-03 12:29 [PATCH 1/2] crypto: vmx - Remove overly verbose printk from AES init routines Michael Ellerman 2018-05-03 12:29 ` Michael Ellerman [this message] 2018-05-11 16:19 ` [PATCH 2/2] crypto: vmx - Remove overly verbose printk from AES XTS init Herbert Xu 2018-05-11 16:19 ` [PATCH 1/2] crypto: vmx - Remove overly verbose printk from AES init routines Herbert Xu 2018-05-14 11:18 ` Michael Ellerman
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=20180503122930.17448-2-mpe@ellerman.id.au \ --to=mpe@ellerman.id.au \ --cc=herbert@gondor.apana.org.au \ --cc=linux-crypto@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linuxppc-dev@ozlabs.org \ --cc=mhcerri@linux.vnet.ibm.com \ --cc=pfsmorigo@linux.vnet.ibm.com \ /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: linkBe 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).