From: Michal Hocko <mhocko@kernel.org>
To: Huaisheng Ye <yehs1@lenovo.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, vbabka@suse.cz,
mgorman@techsingularity.net, pasha.tatashin@oracle.com,
alexander.levin@verizon.com, hannes@cmpxchg.org,
penguin-kernel@I-love.SAKURA.ne.jp, colyli@suse.de,
chengnt@lenovo.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages
Date: Fri, 4 May 2018 15:18:54 +0200 [thread overview]
Message-ID: <20180504131854.GQ4535@dhcp22.suse.cz> (raw)
In-Reply-To: <1525416729-108201-4-git-send-email-yehs1@lenovo.com>
On Fri 04-05-18 14:52:09, Huaisheng Ye wrote:
> realtotalpages is calculated by taking off absent_pages from
> spanned_pages in every zone.
> Debug message of calculate_node_totalpages shall accurately
> indicate that it is real totalpages to avoid ambiguity.
Is the printk actually useful? Why don't we simply remove it? You can
get the information from /proc/zoneinfo so why to litter the dmesg
output?
> Signed-off-by: Huaisheng Ye <yehs1@lenovo.com>
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 1b39db4..9d57db2 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -5967,7 +5967,7 @@ static void __meminit calculate_node_totalpages(struct pglist_data *pgdat,
>
> pgdat->node_spanned_pages = totalpages;
> pgdat->node_present_pages = realtotalpages;
> - printk(KERN_DEBUG "On node %d totalpages: %lu\n", pgdat->node_id,
> + printk(KERN_DEBUG "On node %d realtotalpages: %lu\n", pgdat->node_id,
> realtotalpages);
> }
>
> --
> 1.8.3.1
>
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2018-05-04 13:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 6:52 [PATCH 0/3] Some fixes for mm code optimization Huaisheng Ye
[not found] ` <1525416729-108201-4-git-send-email-yehs1@lenovo.com>
2018-05-04 13:18 ` Michal Hocko [this message]
2018-05-05 2:10 ` [External] Re: [PATCH 3/3] mm/page_alloc: Fix typo in debug info of calculate_node_totalpages Huaisheng HS1 Ye
2018-05-09 7:48 ` Michal Hocko
[not found] ` <1525416729-108201-3-git-send-email-yehs1@lenovo.com>
2018-05-04 13:35 ` [PATCH 2/3] include/linux/gfp.h: use unsigned int in gfp_zone Michal Hocko
2018-05-04 15:40 ` Matthew Wilcox
2018-05-04 17:50 ` [External] " Huaisheng HS1 Ye
2018-05-06 9:32 ` Huaisheng HS1 Ye
2018-05-06 13:48 ` Matthew Wilcox
2018-05-06 16:17 ` Huaisheng HS1 Ye
2018-05-06 18:55 ` Matthew Wilcox
2018-05-07 17:16 ` Huaisheng HS1 Ye
2018-05-07 18:44 ` Matthew Wilcox
2018-05-07 21:25 ` David Sterba
2018-05-08 0:25 ` Matthew Wilcox
2018-05-09 9:36 ` David Sterba
2018-05-15 11:54 ` Matthew Wilcox
2018-05-21 17:06 ` David Sterba
2018-05-09 14:57 ` Huaisheng HS1 Ye
2018-05-08 0:25 ` Huaisheng HS1 Ye
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=20180504131854.GQ4535@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.levin@verizon.com \
--cc=chengnt@lenovo.com \
--cc=colyli@suse.de \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=pasha.tatashin@oracle.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=vbabka@suse.cz \
--cc=yehs1@lenovo.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;
as well as URLs for NNTP newsgroup(s).