From: Michal Hocko <mhocko@suse.com>
To: Nikolay Borisov <nborisov@suse.com>
Cc: akpm@linux-foundation.org, mgorman@suse.de, linux-mm@kvack.org
Subject: Re: [PATCH] mm: Remove ancient/ambiguous comment
Date: Fri, 23 Jun 2017 13:46:17 +0200 [thread overview]
Message-ID: <20170623114617.GO5308@dhcp22.suse.cz> (raw)
In-Reply-To: <1498217717-20945-1-git-send-email-nborisov@suse.com>
On Fri 23-06-17 14:35:17, Nikolay Borisov wrote:
> Currently pg_data_t is just a struct which describes a NUMA node memory
> layout. Let's keep the comment simple and remove ambiguity.
Yes this comment just doesn't make any sense. I would even enhance the
comment and note that on UMA machines there is only a single pg_data_t
that describes the whole memory.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Acked-by: Michal Hocko <mhocko@suse.com>
> ---
> include/linux/mmzone.h | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index ef6a13b7bd3e..c870c65fb945 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -587,10 +587,6 @@ extern struct page *mem_map;
> #endif
>
> /*
> - * The pg_data_t structure is used in machines with CONFIG_DISCONTIGMEM
> - * (mostly NUMA machines?) to denote a higher-level memory zone than the
> - * zone denotes.
> - *
> * On NUMA machines, each NUMA node would have a pg_data_t to describe
> * it's memory layout.
> *
> --
> 2.7.4
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-06-23 11:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 11:35 Nikolay Borisov
2017-06-23 11:46 ` Michal Hocko [this message]
2017-06-23 12:08 ` [PATCH v2] " Nikolay Borisov
2017-06-23 12:14 ` Michal Hocko
2017-06-23 12:22 ` [PATCHi v3] " Nikolay Borisov
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=20170623114617.GO5308@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=nborisov@suse.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