linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Ben Widawsky <ben.widawsky@intel.com>
Cc: linux-mm@kvack.org, Dave Hansen <dave.hansen@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] mm: add comments on pglist_data zones
Date: Wed, 20 May 2020 16:22:35 -0700	[thread overview]
Message-ID: <20200520232235.GD16070@bombadil.infradead.org> (raw)
In-Reply-To: <20200520205443.2757414-1-ben.widawsky@intel.com>

On Wed, May 20, 2020 at 01:54:43PM -0700, Ben Widawsky wrote:
> While making other modifications it was easy to confuse the two struct
> members node_zones and node_zonelists. For those already familiar with
> the code, this might seem to be a silly patch, but it's quite helpful to
> disambiguate the similar-sounding fields
> 
> While here, add a small comment on why nr_zones isn't simply MAX_NR_ZONES

It seems like a real shame to write all this excellent documentation
and not format it as kernel-doc.

> Signed-off-by: Ben Widawsky <ben.widawsky@intel.com>
> ---
>  include/linux/mmzone.h | 14 +++++++++++++-
>  1 file changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git include/linux/mmzone.h include/linux/mmzone.h
> index 1b9de7d220fb..4f7c95e9bad8 100644
> --- include/linux/mmzone.h
> +++ include/linux/mmzone.h
> @@ -665,9 +665,21 @@ struct deferred_split {
>   * per-zone basis.
>   */
>  typedef struct pglist_data {
> +	/*
> +	 * node_zones contains just the zones for THIS node. Not all of the
> +	 * zones may be populated, but it is the full list. It is referenced by
> +	 * this node's node_zonelists as well as other node's node_zonelists.
> +	 */
>  	struct zone node_zones[MAX_NR_ZONES];
> +
> +	/*
> +	 * node_zonelists contains references to all zones in all nodes.
> +	 * Generally the first zones will be references to this node's
> +	 * node_zones.
> +	 */
>  	struct zonelist node_zonelists[MAX_ZONELISTS];
> -	int nr_zones;
> +
> +	int nr_zones; /* number of populated zones in this node */
>  #ifdef CONFIG_FLAT_NODE_MEM_MAP	/* means !SPARSEMEM */
>  	struct page *node_mem_map;
>  #ifdef CONFIG_PAGE_EXTENSION
> -- 
> 2.26.2
> 
> 


  reply	other threads:[~2020-05-20 23:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 20:54 Ben Widawsky
2020-05-20 23:22 ` Matthew Wilcox [this message]
2020-05-21  4:53   ` Ben Widawsky
2020-05-21 11:45     ` Matthew Wilcox

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=20200520232235.GD16070@bombadil.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ben.widawsky@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --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