From: Matthew Wilcox <willy@infradead.org>
To: Mike Rapoport <rppt@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Andrew Morton <akpm@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v2] docs/mm: Physical Memory: add example of interleaving nodes
Date: Sun, 12 Feb 2023 11:50:08 +0000 [thread overview]
Message-ID: <Y+jScFT/qyXSPESp@casper.infradead.org> (raw)
In-Reply-To: <20230212095445.1311627-1-rppt@kernel.org>
On Sun, Feb 12, 2023 at 11:54:45AM +0200, Mike Rapoport wrote:
> +Note, that memory banks may belong to interleaving nodes. In the example
> +below an x86 machine has 16Gbytes or RAM in 4 memory banks, even banks
> +belong to node 0 and odd banks belong to node 1::
s/or RAM/of RAM/
The "Note," is superfluous, you can just write:
Memory banks may belong to interleaved nodes.
And I think we prefer the newer form "GiB" for new documentation.
> +
> + 0 4G 8G 12G 16G
> + +-------------+ +-------------+ +-------------+ +-------------+
> + | node 0 | | node 1 | | node 0 | | node 1 |
> + +-------------+ +-------------+ +-------------+ +-------------+
> +
> + 0 16M 4G
> + +-----+-------+ +-------------+ +-------------+ +-------------+
> + | DMA | DMA32 | | NORMAL | | NORMAL | | NORMAL |
> + +-----+-------+ +-------------+ +-------------+ +-------------+
> +
> +In such case node 0 will span from 0 to 12 Gbytes and node 1 will span from
> +4 to 16 Gbytes.
s/such/this/ (and I'd use GiB again)
next prev parent reply other threads:[~2023-02-12 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 9:54 [PATCH v2] docs/mm: Physical Memory: add example of interleaving nodes Mike Rapoport
2023-02-12 11:50 ` Matthew Wilcox [this message]
2023-02-12 14:47 ` Mike Rapoport
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=Y+jScFT/qyXSPESp@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lstoakes@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=rppt@kernel.org \
--cc=vbabka@suse.cz \
/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