From: David Hildenbrand <david@redhat.com>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/page_owner: Use helper function zone_end_pfn() to get end_pfn
Date: Tue, 26 Jan 2021 12:23:32 +0100 [thread overview]
Message-ID: <25c538a0-8d10-7c2c-6562-52a91ac158a6@redhat.com> (raw)
In-Reply-To: <20210123070538.5861-1-linmiaohe@huawei.com>
On 23.01.21 08:05, Miaohe Lin wrote:
> Commit 108bcc96ef70 ("mm: add & use zone_end_pfn() and zone_spans_pfn()")
> introduced the helper zone_end_pfn() to calculate the zone end pfn. But
> pagetypeinfo_showmixedcount_print forgot to use it. And the initialization
> of local variable pfn is duplicated, remove one.
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/page_owner.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/page_owner.c b/mm/page_owner.c
> index af464bb7fbe7..d15c7c4994f5 100644
> --- a/mm/page_owner.c
> +++ b/mm/page_owner.c
> @@ -263,8 +263,8 @@ void pagetypeinfo_showmixedcount_print(struct seq_file *m,
> struct page *page;
> struct page_ext *page_ext;
> struct page_owner *page_owner;
> - unsigned long pfn = zone->zone_start_pfn, block_end_pfn;
> - unsigned long end_pfn = pfn + zone->spanned_pages;
> + unsigned long pfn, block_end_pfn;
> + unsigned long end_pfn = zone_end_pfn(zone);
> unsigned long count[MIGRATE_TYPES] = { 0, };
> int pageblock_mt, page_mt;
> int i;
>
Looks a little weird that we initialize "end_pfn" directly and "pfn"
not. I'd make this consistent.
Anyhow
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2021-01-26 11:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 7:05 Miaohe Lin
2021-01-26 11:23 ` David Hildenbrand [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=25c538a0-8d10-7c2c-6562-52a91ac158a6@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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