From: sashiko-bot@kernel.org
To: "Harald Freudenberger" <freude@linux.ibm.com>
Cc: linux-s390@vger.kernel.org, "Heiko Carstens" <hca@linux.ibm.com>,
"Vasily Gorbik" <gor@linux.ibm.com>,
"Alexander Gordeev" <agordeev@linux.ibm.com>,
"Christian Borntraeger" <borntraeger@linux.ibm.com>
Subject: Re: [PATCH v3 2/2] s390/ap: Cap AP maximum message size adjustable via module parameter
Date: Tue, 13 Oct 2026 13:52:25 +0000 [thread overview]
Message-ID: <sashiko-outbox-169867@kernel.org> (raw)
In-Reply-To: <20261013134422.64155-3-freude@linux.ibm.com>
> With AP bus now supporting the new APMLM field with PQAP/TAPQ the AP
> max message size could be raised up to 960KB. As this amount of memory
> is tried to get allocated on each AP request/reply it would quickly
> cause some memory problems.
>
> Introduce a reasonable default upper limit
> AP_DEFAULT_MAX_MSG_SIZE_LIMIT (72KB) and expose it via a read-only
> module parameter 'max_msg_size_limit'. When creating an AP card, clip
> the calculated AP max message size from the hardware info fetched via
> PQAP/TAPQ to this upper limit and log a debug feature warning
> (AP_DBF_WARN) if the card's reported limit exceeds it.
>
> Also define some lower limit AP_MIN_MSG_SIZE (12KB) and ensure during
> module init that a user-supplied max_msg_size_limit parameter is not
> lower than this minimum, adjusting it with a warning if necessary.
>
> Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261013134422.64155-1-freude@linux.ibm.com?part=2
prev parent reply other threads:[~2026-10-13 13:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:44 [PATCH v3 0/2] Support APMLM field with PQAP/TAPQ instruction Harald Freudenberger
2026-10-13 13:44 ` [PATCH v3 1/2] s390/ap: Support new " Harald Freudenberger
2026-10-13 13:52 ` sashiko-bot
2026-10-13 13:44 ` [PATCH v3 2/2] s390/ap: Cap AP maximum message size adjustable via module parameter Harald Freudenberger
2026-10-13 13:52 ` sashiko-bot [this message]
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=sashiko-outbox-169867@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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