From: Mike Rapoport <rppt@kernel.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: 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>,
"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 v3] docs/mm: Physical Memory: add example of interleaving nodes
Date: Tue, 21 Feb 2023 08:52:25 +0200 [thread overview]
Message-ID: <Y/RqKbBeXLswC1AR@kernel.org> (raw)
In-Reply-To: <20230213154447.1631847-1-rppt@kernel.org>
Ping?
On Mon, Feb 13, 2023 at 05:44:47PM +0200, Mike Rapoport wrote:
> From: "Mike Rapoport (IBM)" <rppt@kernel.org>
>
> Add an example of memory layout with interleaving nodes where even memory
> banks belong to node 0 and odd memory banks belong to node 1
>
> Suggested-by: Michal Hocko <mhocko@kernel.org>
> Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
> ---
>
> v3:
> * Fix typos and wording (Matthew)
>
> v2: https://lore.kernel.org/all/20230212095445.1311627-1-rppt@kernel.org
> * Wording update (Bagas)
> * Add forgotten Suggested-by
>
> v1: https://lore.kernel.org/all/20230211102207.1267058-1-rppt@kernel.org
> Documentation/mm/physical_memory.rst | 19 +++++++++++++++++++
> 1 file changed, 19 insertions(+)
>
> diff --git a/Documentation/mm/physical_memory.rst b/Documentation/mm/physical_memory.rst
> index 3f3c02aa6e6e..863ddcd0b291 100644
> --- a/Documentation/mm/physical_memory.rst
> +++ b/Documentation/mm/physical_memory.rst
> @@ -114,6 +114,25 @@ RAM equally split between two nodes, there will be ``ZONE_DMA32``,
> | DMA32 | NORMAL | MOVABLE | | NORMAL | MOVABLE |
> +---------+----------+-----------+ +------------+-------------+
>
> +
> +Memory banks may belong to interleaving nodes. In the example below an x86
> +machine has 16 Gbytes of 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 this case node 0 will span from 0 to 12 Gbytes and node 1 will span from
> +4 to 16 Gbytes.
> +
> .. _nodes:
>
> Nodes
>
> base-commit: e076f253283c3e55a128fa9665c0e6cd8146948d
> --
> 2.35.1
>
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-02-21 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 15:44 Mike Rapoport
2023-02-13 15:52 ` David Hildenbrand
2023-02-21 6:52 ` Mike Rapoport [this message]
2023-02-21 14:31 ` Jonathan Corbet
2023-03-14 18:54 ` Jonathan Corbet
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/RqKbBeXLswC1AR@kernel.org \
--to=rppt@kernel.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=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