public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Harald Freudenberger <freude@linux.ibm.com>
To: Holger Dengler <dengler@linux.ibm.com>
Cc: ifranzki@linux.ibm.com, fcallies@linux.ibm.com,
	hca@linux.ibm.com, gor@linux.ibm.com, agordeev@linux.ibm.com,
	linux-s390@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH v2 05/20] s390/zcrypt: Introduce cprb mempool for cca misc functions
Date: Tue, 25 Mar 2025 09:26:51 +0100	[thread overview]
Message-ID: <3325245358b26e84cbbcd4b80ecaba9c@linux.ibm.com> (raw)
In-Reply-To: <a9e5cebe-7d68-46df-a194-d6ef393322fb@linux.ibm.com>

On 2025-03-18 15:16, Holger Dengler wrote:
> On 04/03/2025 18:21, Harald Freudenberger wrote:
>> Introduce a cprb mempool for the zcrypt cca misc functions
>> (zcrypt_ccamisc.*) do some preparation rework to support
>> a do-not-allocate path through some zcrypt cca misc functions.
>> 
>> The mempool is by default space for 4 cprbs with each 16KB.
>> For CCA a CPRB needs to hold the request and the reply, so
>> the pool items only support requests/replies with a limit of
>> about 8KB. The minimal number of items in the mempool can get
>> adjusted via module parameter zcrypt.cca_cprbpool_min_items
>> on module load.
>> 
>> This is only part of an rework to support a new xflag
>> ZCRYPT_XFLAG_NOMEMALLOC but not yet complete.
>> 
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
> 
> One minor comment below. Beside that
> Reviewed-by: Holger Dengler <dengler@linux.ibm.com>
> 
>> ---
>>  drivers/s390/crypto/zcrypt_api.c     |  13 ++-
>>  drivers/s390/crypto/zcrypt_api.h     |   2 +
>>  drivers/s390/crypto/zcrypt_ccamisc.c | 116 
>> ++++++++++++++++++++-------
>>  drivers/s390/crypto/zcrypt_ccamisc.h |   1 +
>>  4 files changed, 101 insertions(+), 31 deletions(-)
>> 
> [...]
>> diff --git a/drivers/s390/crypto/zcrypt_ccamisc.c 
>> b/drivers/s390/crypto/zcrypt_ccamisc.c
>> index 521baaea06ff..2c2ca2d67e2d 100644
>> --- a/drivers/s390/crypto/zcrypt_ccamisc.c
>> +++ b/drivers/s390/crypto/zcrypt_ccamisc.c
> [...]
>> @@ -229,7 +241,15 @@ static int alloc_and_prep_cprbmem(size_t 
>> paramblen,
>>  	 * allocate consecutive memory for request CPRB, request param
>>  	 * block, reply CPRB and reply param block
>>  	 */
>> -	cprbmem = kcalloc(2, cprbplusparamblen, GFP_KERNEL);
>> +	if (xflags & ZCRYPT_XFLAG_NOMEMALLOC) {
>> +		if (cprb_mempool &&
>> +		    2 * cprbplusparamblen <= CPRB_MEMPOOL_ITEM_SIZE) {
>> +			cprbmem = mempool_alloc_preallocated(cprb_mempool);
>> +			memset(cprbmem, 0, 2 * cprbplusparamblen);
>> +		}
>> +	} else {
> 
> Just a nit: let the compiler decide, if code should be duplicated or 
> not.
> 
> if (xflags & ZCRYPT_XFLAG_NOMEMALLOC) {
> 	size_t len = 2 * cprbplusparamblen;
> 
> 	if (cprb_mempool && len <= CPRB_MEMPOOL_ITEM_SIZE) {
> 		cprbmem = mempool_alloc_preallocated(cprb_mempool);
> 		memset(cprbmem, 0, len);
> 	}
> } else {
> 
>> +		cprbmem = kcalloc(2, cprbplusparamblen, GFP_KERNEL);
>> +	}
>>  	if (!cprbmem)
>>  		return -ENOMEM;
>> 
> [...]

It was not my intention to outsmart the compier when writing this code.
However, changed to your suggestion -> v3

  reply	other threads:[~2025-03-25  8:27 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 17:20 [PATCH v2 00/20] AP bus/zcrypt/pkey/paes no-mem-alloc patches Harald Freudenberger
2025-03-04 17:20 ` [PATCH v2 01/20] s390/ap: Move response_type struct into ap_msg struct Harald Freudenberger
2025-03-17  9:38   ` Holger Dengler
2025-03-24 14:34     ` Harald Freudenberger
2025-03-04 17:20 ` [PATCH v2 02/20] s390/ap/zcrypt: Rework AP message buffer allocation Harald Freudenberger
2025-03-17 13:57   ` Holger Dengler
2025-03-04 17:20 ` [PATCH v2 03/20] s390/ap: Introduce ap message buffer pool Harald Freudenberger
2025-03-17 16:14   ` Holger Dengler
2025-03-24 14:41     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 04/20] s390/ap/zcrypt: New xflag parameter and extension of the ap msg flags Harald Freudenberger
2025-03-18 12:16   ` Holger Dengler
2025-03-24 15:52     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 05/20] s390/zcrypt: Introduce cprb mempool for cca misc functions Harald Freudenberger
2025-03-18 14:16   ` Holger Dengler
2025-03-25  8:26     ` Harald Freudenberger [this message]
2025-03-04 17:21 ` [PATCH v2 06/20] s390/zcrypt: Introduce cprb mempool for ep11 " Harald Freudenberger
2025-03-18 15:16   ` Holger Dengler
2025-03-25  8:36     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 07/20] s390/zcrypt: Rework zcrypt function zcrypt_device_status_mask_ext Harald Freudenberger
2025-03-19 11:03   ` Holger Dengler
2025-03-25  9:24     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 08/20] s390/zcrypt: Introduce pre-allocated device status array for cca misc Harald Freudenberger
2025-03-19 14:31   ` Holger Dengler
2025-03-25 10:51     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 09/20] s390/zcrypt: Introduce pre-allocated device status array for ep11 misc Harald Freudenberger
2025-03-19 18:02   ` Holger Dengler
2025-03-25 11:09     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 10/20] s390/zcrypt/pkey: Rework cca findcard() implementation and callers Harald Freudenberger
2025-03-19 17:58   ` Holger Dengler
2025-03-25 13:02     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 11/20] s390/zcrypt/pkey: Rework ep11 " Harald Freudenberger
2025-03-20  8:30   ` Holger Dengler
2025-03-25 13:12     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 12/20] s390/zcrypt: Rework cca misc functions kmallocs to use the cprb mempool Harald Freudenberger
2025-03-20  9:31   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 13/20] s390/zcrypt: Add small mempool for cca info list entries Harald Freudenberger
2025-03-20 14:34   ` Holger Dengler
2025-03-25 13:32     ` Harald Freudenberger
2025-03-20 16:05   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 14/20] s390/zcrypt: Locate ep11_domain_query_info onto the stack instead of kmalloc Harald Freudenberger
2025-03-20 14:41   ` Holger Dengler
2025-03-25 14:04     ` Harald Freudenberger
2025-03-04 17:21 ` [PATCH v2 15/20] s390/zcrypt: Rework ep11 misc functions to use cprb mempool Harald Freudenberger
2025-03-20 15:18   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 16/20] s390/zcrypt: Add small mempool for ep11 card info list entries Harald Freudenberger
2025-03-20 16:09   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 17/20] s390/pkey: Rework CCA pkey handler to use stack for small memory allocs Harald Freudenberger
2025-03-21  9:05   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 18/20] s390/pkey: Rework EP11 " Harald Freudenberger
2025-03-21  9:06   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 19/20] s390/zcrypt/pkey: Provide and pass xflags within pkey and zcrypt layers Harald Freudenberger
2025-03-20 16:30   ` Holger Dengler
2025-03-04 17:21 ` [PATCH v2 20/20] s390/pkey/crypto: Introduce xflags param for pkey in-kernel API Harald Freudenberger
2025-03-20 16:34   ` Holger Dengler
2025-03-20 16:40 ` [PATCH v2 00/20] AP bus/zcrypt/pkey/paes no-mem-alloc patches Holger Dengler

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=3325245358b26e84cbbcd4b80ecaba9c@linux.ibm.com \
    --to=freude@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=dengler@linux.ibm.com \
    --cc=fcallies@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=ifranzki@linux.ibm.com \
    --cc=linux-s390@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