linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Naoya Horiguchi <naoya.horiguchi@linux.dev>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, willy@infradead.org,
	naoya.horiguchi@nec.com, osalvador@suse.de
Subject: Re: [PATCH v2 3/3] mm/page_alloc: remove unnecessary next_page in break_down_buddy_pages
Date: Tue, 26 Sep 2023 20:34:17 +0900	[thread overview]
Message-ID: <20230926113417.GC1539169@ik1-406-35019.vs.sakura.ne.jp> (raw)
In-Reply-To: <20230826154745.4019371-4-shikemeng@huaweicloud.com>

On Sat, Aug 26, 2023 at 11:47:45PM +0800, Kemeng Shi wrote:
> The next_page is only used to forward page in case target is in second
> harf range. Move forward page directly to remove unnecessary next_page.

s/harf/half/

> 
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>

Acked-by: Naoya Horiguchi <naoya.horiguchi@nec.com>

> ---
>  mm/page_alloc.c | 6 ++----
>  1 file changed, 2 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index bb74b40dc195..1c35ee022dde 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -6492,20 +6492,18 @@ static void break_down_buddy_pages(struct zone *zone, struct page *page,
>  				   int migratetype)
>  {
>  	unsigned long size = 1 << high;
> -	struct page *current_buddy, *next_page;
> +	struct page *current_buddy;
>  
>  	while (high > low) {
>  		high--;
>  		size >>= 1;
>  
>  		if (target >= &page[size]) {
> -			next_page = page + size;
>  			current_buddy = page;
> +			page = page + size;
>  		} else {
> -			next_page = page;
>  			current_buddy = page + size;
>  		}
> -		page = next_page;
>  
>  		if (set_page_guard(zone, current_buddy, high, migratetype))
>  			continue;
> -- 
> 2.30.0
> 
> 
> 


      reply	other threads:[~2023-09-26 11:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-26 15:47 [PATCH v2 0/3] Fixes and cleanups to break_down_buddy_pages Kemeng Shi
2023-08-26 15:47 ` [PATCH v2 1/3] mm/page_alloc: correct start page when guard page debug is enabled Kemeng Shi
2023-08-28 15:21   ` Naoya Horiguchi
2023-08-30  6:27     ` Kemeng Shi
2023-09-26 11:33       ` Naoya Horiguchi
2023-09-27  1:13         ` Kemeng Shi
2023-08-26 15:47 ` [PATCH v2 2/3] mm/page_alloc: remove unnecessary check in break_down_buddy_pages Kemeng Shi
2023-09-26 11:34   ` Naoya Horiguchi
2023-08-26 15:47 ` [PATCH v2 3/3] mm/page_alloc: remove unnecessary next_page " Kemeng Shi
2023-09-26 11:34   ` Naoya Horiguchi [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=20230926113417.GC1539169@ik1-406-35019.vs.sakura.ne.jp \
    --to=naoya.horiguchi@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.com \
    --cc=osalvador@suse.de \
    --cc=shikemeng@huaweicloud.com \
    --cc=willy@infradead.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