All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Laight <david.laight.linux@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Sahil Chandna <chandna.sahil@gmail.com>,
	akpm@linux-foundation.org, david@redhat.com,
	lorenzo.stoakes@oracle.com, mhocko@suse.com, vbabka@suse.cz,
	rppt@kernel.org, surenb@google.com, hannes@cmpxchg.org,
	shakeel.butt@linux.dev, zhengqi.arch@bytedance.com,
	Liam.Howlett@oracle.com, weixugc@google.com,
	axelrasmussen@google.com, yuanchu@google.com,
	yosry.ahmed@linux.dev, nphamcs@gmail.com,
	chengming.zhou@linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] mm/pagewalk: use min() macro instead of manual ternary
Date: Tue, 18 Nov 2025 16:56:09 +0000	[thread overview]
Message-ID: <20251118165609.16c09e74@pumpkin> (raw)
In-Reply-To: <aRyOWrARRlUCeEz6@casper.infradead.org>

On Tue, 18 Nov 2025 15:18:50 +0000
Matthew Wilcox <willy@infradead.org> wrote:

> On Tue, Nov 18, 2025 at 10:45:37AM +0000, David Laight wrote:
> > On Tue, 18 Nov 2025 11:38:49 +0530
> > Sahil Chandna <chandna.sahil@gmail.com> wrote:  
> > > +++ b/mm/pagewalk.c
> > > @@ -313,7 +313,7 @@ static unsigned long hugetlb_entry_end(struct hstate *h, unsigned long addr,
> > >  				       unsigned long end)
> > >  {
> > >  	unsigned long boundary = (addr & huge_page_mask(h)) + huge_page_size(h);
> > > -	return boundary < end ? boundary : end;
> > > +	return min(boundary, end);  
> > 
> > You can remove the temporary:
> > 	return min((addr & huge_page_mask(h)) + huge_page_size(h), end);  
> 
> You can, but I'm not sure that's better.  What would be better is:
> 
> 	unsigned long boundary = (addr | ~huge_page_mask(h)) + 1;
> 	return min(boundary, end);
> 
> if you insist, we could do:
> 
> 	return min((addr | ~huge_page_mask(h)) + 1, end);

Indeed...

	David


  reply	other threads:[~2025-11-18 16:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-18  6:08 [PATCH 0/3] mm: Coccinelle-driven cleanups across memory management code Sahil Chandna
2025-11-18  6:08 ` [PATCH 1/3] mm/pagewalk: use min() macro instead of manual ternary Sahil Chandna
2025-11-18 10:19   ` Markus Elfring
2025-11-18 10:45   ` David Laight
2025-11-18 15:18     ` Matthew Wilcox
2025-11-18 16:56       ` David Laight [this message]
2025-11-18  6:08 ` [PATCH 2/3] mm/vmscan: use %pe to print PTR_ERR() values Sahil Chandna
2025-11-18 13:15   ` Markus Elfring
2025-11-19  1:52   ` SeongJae Park
2025-11-18  6:08 ` [PATCH 3/3] mm/zswap: " Sahil Chandna
2025-11-18 13:20   ` Markus Elfring
2025-11-18 15:11     ` Matthew Wilcox
2025-11-18 19:28       ` Markus Elfring
2025-11-18 15:46   ` Yosry Ahmed
2025-11-19  1:50   ` SeongJae Park
2025-11-19 12:50   ` Nhat Pham

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=20251118165609.16c09e74@pumpkin \
    --to=david.laight.linux@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=chandna.sahil@gmail.com \
    --cc=chengming.zhou@linux.dev \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=nphamcs@gmail.com \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=weixugc@google.com \
    --cc=willy@infradead.org \
    --cc=yosry.ahmed@linux.dev \
    --cc=yuanchu@google.com \
    --cc=zhengqi.arch@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.