mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danny Tsen <dtsen@linux.ibm.com>
To: "Elliott, Robert (Servers)" <elliott@hpe.com>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Cc: "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
	"leitao@debian.org" <leitao@debian.org>,
	"nayna@linux.ibm.com" <nayna@linux.ibm.com>,
	"appro@cryptogams.org" <appro@cryptogams.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"ltcgcw@linux.vnet.ibm.com" <ltcgcw@linux.vnet.ibm.com>,
	"dtsen@us.ibm.com" <dtsen@us.ibm.com>
Subject: RE: [PATCH v3 1/6] Update Kconfig and Makefile.
Date: Fri, 17 Feb 2023 16:20:06 -0600	[thread overview]
Message-ID: <02d4b4b5-4292-aef0-8e20-7ec031348e91@linux.ibm.com> (raw)
In-Reply-To: <MW5PR84MB1842DB9DF917B9B3B83A005BABA19@MW5PR84MB1842.NAMPRD84.PROD.OUTLOOK.COM>

Hi Robert,

Power10+ means Power10 or later.  Other modes were not stripped by the 
perl script.

Thanks for the comments I will fix the suggestions.

-Danny

On 2/17/23 3:44 PM, Elliott, Robert (Servers) wrote:
>> +config CRYPTO_P10_AES_GCM
>> +	tristate "Stitched AES/GCM acceleration support on P10+ CPU (PPC)"
>> +	depends on PPC64 && POWER10_CPU && CPU_LITTLE_ENDIAN
>> +	select CRYPTO_LIB_AES
>> +	select CRYPTO_ALGAPI
>> +	select CRYPTO_AEAD
>> +	default m
>> +	help
>> +	  Support for cryptographic acceleration instructions on Power10+ CPU.
>> +	    This module supports stitched acceleration for AES/GCM in
>> hardware.
> Is "Power10+" a specific architecture or does that mean "Power10 or later"?
>
> Please follow the newer wording conventions for the menu item and
> help text, more like:
>
> config CRYPTO_AES_GCM_PPC_P10
>          tristate "AEAD cipher: AES in GCM mode (Power10)"
>
>          help
>            AEAD cipher: AES cipher algorithms (FIPS-197) with
> 	   GCM (Galois/Counter Mode) authenticated encryption mode (NIST SP800-38D)
>
>            Architecture: powerpc64 using:
>            - little-endian
>            - Power10 features
>
>            [some description here]
>
> Also, all the other powerpc cra_driver_names follow
> 	alg-arch
> not
> 	arch-alg
>
> so
> 	.base.cra_driver_name	= "p10_aes_gcm",
> might be better as
> 	.base.cra_driver_name	= "aes-gcm-p10",
>
> Patch 4 seems to have code for lots of other modes like CBC and XTS.
> Does the perl script strip out all of that?
>
>
>

  reply	other threads:[~2023-02-17 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 16:17 [PATCH v3 0/6] crypto: Accelerated AES/GCM stitched implementation Danny Tsen
2023-02-17 16:18 ` [PATCH v3 1/6] Update Kconfig and Makefile Danny Tsen
2023-02-17 21:44   ` Elliott, Robert (Servers)
2023-02-17 22:20     ` Danny Tsen [this message]
2023-02-17 16:18 ` [PATCH v3 2/6] Glue code for AES/GCM stitched implementation Danny Tsen
2023-02-17 16:18 ` [PATCH v3 3/6] An accelerated " Danny Tsen
2023-02-17 16:18 ` [PATCH v3 4/6] Supporting functions for AES Danny Tsen
2023-02-17 16:18 ` [PATCH v3 5/6] Supporting functions for ghash Danny Tsen
2023-02-17 16:18 ` [PATCH v3 6/6] A perl script to process PowerPC assembler source Danny Tsen

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=02d4b4b5-4292-aef0-8e20-7ec031348e91@linux.ibm.com \
    --to=dtsen@linux.ibm.com \
    --cc=appro@cryptogams.org \
    --cc=dtsen@us.ibm.com \
    --cc=elliott@hpe.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=leitao@debian.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltcgcw@linux.vnet.ibm.com \
    --cc=nayna@linux.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: 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

all inboxes | Powered by JetHome®