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 03/20] s390/ap: Introduce ap message buffer pool
Date: Mon, 24 Mar 2025 15:41:18 +0100 [thread overview]
Message-ID: <31aa895585a8302597d41b989d0c196c@linux.ibm.com> (raw)
In-Reply-To: <1935a111-c0a3-4d7e-85f5-f7218253f1fc@linux.ibm.com>
On 2025-03-17 17:14, Holger Dengler wrote:
> On 04/03/2025 18:20, Harald Freudenberger wrote:
>> There is a need for a do-not-allocate-memory path through the
>> ap bus layer. When ap_init_apmsg() with use_mempool set to true
>> is called, instead of kmalloc() the ap message buffer is
>> allocated from the ap_msg_pool. This pool only holds a limited
>> amount of buffers: ap_msg_pool_min_items with the item size
>> AP_DEFAULT_MAX_MSG_SIZE and exactly one of these items (if available)
>> is returned if ap_init_apmsg() with the use_mempool arg set to true
>> is called. When this pool is exhausted and use_mempool is set true,
>> ap_init_apmsg() returns -ENOMEM without any attempt to allocate
>> memory.
>>
>> Default values for this mempool of ap messages is:
>> * Each buffer is 12KB (that is the default AP bus size
>> and all the urgend messages should fit into this space).
>
> typo: urgent
>
done -> v3
>> * Minimum items held in the pool is 8. This value is adjustable
>> via module parameter ap.msgpool_min_items.
>>
>> The zcrypt layer may use this flag to indicate to the ap bus
>> that the processing path for this message should not allocate
>> memory but should use pre-allocated memory buffer instead.
>> This is to prevent deadlocks with crypto and io for example
>> with encrypted swap volumes.
>>
>> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
>
> With the typo and the changed indent (see comment below)
> Reviewed-by: Holger Dengler <dengler@linux.ibm.com>
>
>> ---
>> drivers/s390/crypto/ap_bus.c | 57
>> ++++++++++++++++++++++++++++----
>> drivers/s390/crypto/ap_bus.h | 9 ++---
>> drivers/s390/crypto/zcrypt_api.c | 10 +++---
>> 3 files changed, 60 insertions(+), 16 deletions(-)
>>
> [...]
>> diff --git a/drivers/s390/crypto/ap_bus.h
>> b/drivers/s390/crypto/ap_bus.h
>> index 483231bcdea6..a7bd44e5cc76 100644
>> --- a/drivers/s390/crypto/ap_bus.h
>> +++ b/drivers/s390/crypto/ap_bus.h
>> @@ -233,11 +233,12 @@ struct ap_message {
>> struct ap_message *);
>> };
>>
>> -#define AP_MSG_FLAG_SPECIAL 0x0001 /* flag msg as 'special' with
>> NQAP */
>> -#define AP_MSG_FLAG_USAGE 0x0002 /* CCA, EP11: usage (no admin)
>> msg */
>> -#define AP_MSG_FLAG_ADMIN 0x0004 /* CCA, EP11: admin (=control)
>> msg */
>> +#define AP_MSG_FLAG_SPECIAL 0x0001 /* flag msg as 'special' with
>> NQAP */
>> +#define AP_MSG_FLAG_USAGE 0x0002 /* CCA, EP11: usage (no admin)
>> msg */
>> +#define AP_MSG_FLAG_ADMIN 0x0004 /* CCA, EP11: admin (=control)
>> msg */
>> +#define AP_MSG_FLAG_MEMPOOL 0x0008 /* ap msg buffer allocated from
>> mempool */
>
> Please do not change the indent here. The change is not required, but
> it makes the life of reviewers much harder.
>
corrected -> v3
>>
>> -int ap_init_apmsg(struct ap_message *ap_msg);
>> +int ap_init_apmsg(struct ap_message *ap_msg, bool use_mempool);
>> void ap_release_apmsg(struct ap_message *ap_msg);
>>
>> enum ap_sm_wait ap_sm_event(struct ap_queue *aq, enum ap_sm_event
>> event);
> [...]
next prev parent reply other threads:[~2025-03-24 14:41 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 [this message]
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
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=31aa895585a8302597d41b989d0c196c@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