From: Mel Gorman <mgorman@techsingularity.net>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, baolin.wang@linux.alibaba.com,
david@redhat.com, willy@infradead.org
Subject: Re: [PATCH 2/2] mm/page_alloc: use get_pfnblock_migratetype to avoid extra page_to_pfn
Date: Mon, 21 Aug 2023 13:21:02 +0100 [thread overview]
Message-ID: <20230821122102.uybh63ifycgmqm3a@techsingularity.net> (raw)
In-Reply-To: <20230811115945.3423894-3-shikemeng@huaweicloud.com>
On Fri, Aug 11, 2023 at 07:59:45PM +0800, Kemeng Shi wrote:
> We have get_pageblock_migratetype and get_pfnblock_migratetype to get
> migratetype of page. get_pfnblock_migratetype accepts both page and pfn
> from caller while get_pageblock_migratetype only accept page and get pfn
> with page_to_pfn from page.
> In case we already record pfn of page, we can simply call
> get_pfnblock_migratetype to avoid a page_to_pfn.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
Acked-by: Mel Gorman <mgorman@techsingularity.net>
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2023-08-21 12:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230811115945.3423894-1-shikemeng@huaweicloud.com>
2023-08-11 11:59 ` [PATCH 1/2] mm/page_alloc: remove unnecessary inner __get_pfnblock_flags_mask Kemeng Shi
2023-08-11 4:28 ` Matthew Wilcox
2023-08-21 12:20 ` Mel Gorman
2023-08-21 21:23 ` Johannes Weiner
[not found] ` <20230811115945.3423894-3-shikemeng@huaweicloud.com>
2023-08-21 12:21 ` Mel Gorman [this message]
2023-08-21 21:24 ` [PATCH 2/2] mm/page_alloc: use get_pfnblock_migratetype to avoid extra page_to_pfn Johannes Weiner
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=20230821122102.uybh63ifycgmqm3a@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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