From: Vasily Gorbik <gor@linux.ibm.com>
To: Qasim Ijaz <qasdev00@gmail.com>
Cc: agordeev@linux.ibm.com, gerald.schaefer@linux.ibm.com,
hca@linux.ibm.com, borntraeger@linux.ibm.com,
svens@linux.ibm.com, linux-s390@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390/mm: Simplify gap clamping in mmap_base() using clamp()
Date: Sat, 22 Feb 2025 00:55:43 +0100 [thread overview]
Message-ID: <your-ad-here.call-01740182143-ext-5271@work.hours> (raw)
In-Reply-To: <20250204162508.12335-1-qasdev00@gmail.com>
On Tue, Feb 04, 2025 at 04:25:08PM +0000, Qasim Ijaz wrote:
> mmap_base() has logic to ensure that the variable "gap" stays within the
> range defined by "gap_min" and "gap_max". Replace this with the clamp()
> macro to shorten and simplify code.
>
> Signed-off-by: Qasim Ijaz <qasdev00@gmail.com>
> ---
> arch/s390/mm/mmap.c | 6 +-----
> 1 file changed, 1 insertion(+), 5 deletions(-)
>
> diff --git a/arch/s390/mm/mmap.c b/arch/s390/mm/mmap.c
> index 76f376876e0d..a3d3e09a2828 100644
> --- a/arch/s390/mm/mmap.c
> +++ b/arch/s390/mm/mmap.c
> @@ -63,11 +63,7 @@ static inline unsigned long mmap_base(unsigned long rnd,
> */
> gap_min = SZ_128M;
> gap_max = (STACK_TOP / 6) * 5;
> -
> - if (gap < gap_min)
> - gap = gap_min;
> - else if (gap > gap_max)
> - gap = gap_max;
> + gap = clamp(gap, gap_min, gap_max);
>
> return PAGE_ALIGN(STACK_TOP - gap - rnd);
> }
> --
Reviewed-by: Vasily Gorbik <gor@linux.ibm.com>
Applied, with a fixup removing the gap_min and gap_max variables as
Alexander proposed and aligning with your patch for x86. Thank you!
https://lore.kernel.org/all/174014934373.10177.13398467994659612713.tip-bot2@tip-bot2/
next prev parent reply other threads:[~2025-02-21 23:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 16:25 [PATCH] s390/mm: Simplify gap clamping in mmap_base() using clamp() Qasim Ijaz
2025-02-14 10:58 ` Alexander Gordeev
2025-02-21 23:55 ` Vasily Gorbik [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-15 12:31 Qasim Ijaz
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=your-ad-here.call-01740182143-ext-5271@work.hours \
--to=gor@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gerald.schaefer@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=qasdev00@gmail.com \
--cc=svens@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