From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Mike Rapoport <rppt@kernel.org>, Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Lorenzo Stoakes <lstoakes@gmail.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
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] docs/mm: Physical Memory: add example of interleaving nodes
Date: Sat, 11 Feb 2023 19:31:18 +0700 [thread overview]
Message-ID: <330367aa-6d34-2341-9d24-5f2e09aecfdf@gmail.com> (raw)
In-Reply-To: <20230211102207.1267058-1-rppt@kernel.org>
On 2/11/23 17:22, 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::
> +
> +
> + 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 Gbytes to 16 Gbytes.
> +
What about "... and node 1 will span from 4 to 16 Gbytes"?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-02-11 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 10:22 [PATCH] docs/mm: Physical Memory: add example of interleaving nodes Mike Rapoport
2023-02-11 12:31 ` Bagas Sanjaya [this message]
2023-02-11 12:39 ` 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=330367aa-6d34-2341-9d24-5f2e09aecfdf@gmail.com \
--to=bagasdotme@gmail.com \
--cc=akpm@linux-foundation.org \
--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 \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).