linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] docs/mm: Physical Memory: add example of interleaving nodes
@ 2023-02-11 10:22 Mike Rapoport
  2023-02-11 12:31 ` Bagas Sanjaya
  0 siblings, 1 reply; 3+ messages in thread
From: Mike Rapoport @ 2023-02-11 10:22 UTC (permalink / raw)
  To: Jonathan Corbet
  Cc: Andrew Morton, Bagas Sanjaya, David Hildenbrand, Johannes Weiner,
	Lorenzo Stoakes, Matthew Wilcox (Oracle), Mel Gorman,
	Michal Hocko, Mike Rapoport, Vlastimil Babka, linux-doc,
	linux-kernel, linux-mm

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

Signed-off-by: Mike Rapoport (IBM) <rppt@kernel.org>
---

As per Michal's request add an example of interleaving nodes.
This is based on Jon's docs-next of Wednesday.

 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..eb9a7a6d3216 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   |
   +---------+----------+-----------+ +------------+-------------+
 
+
+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.
+
 .. _nodes:
 
 Nodes

base-commit: e076f253283c3e55a128fa9665c0e6cd8146948d
-- 
2.35.1



^ permalink raw reply related	[flat|nested] 3+ messages in thread

* Re: [PATCH] docs/mm: Physical Memory: add example of interleaving nodes
  2023-02-11 10:22 [PATCH] docs/mm: Physical Memory: add example of interleaving nodes Mike Rapoport
@ 2023-02-11 12:31 ` Bagas Sanjaya
  2023-02-11 12:39   ` Mike Rapoport
  0 siblings, 1 reply; 3+ messages in thread
From: Bagas Sanjaya @ 2023-02-11 12:31 UTC (permalink / raw)
  To: Mike Rapoport, Jonathan Corbet
  Cc: Andrew Morton, David Hildenbrand, Johannes Weiner,
	Lorenzo Stoakes, Matthew Wilcox (Oracle), Mel Gorman,
	Michal Hocko, Vlastimil Babka, linux-doc, linux-kernel, linux-mm

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



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] docs/mm: Physical Memory: add example of interleaving nodes
  2023-02-11 12:31 ` Bagas Sanjaya
@ 2023-02-11 12:39   ` Mike Rapoport
  0 siblings, 0 replies; 3+ messages in thread
From: Mike Rapoport @ 2023-02-11 12:39 UTC (permalink / raw)
  To: Bagas Sanjaya
  Cc: Jonathan Corbet, Andrew Morton, David Hildenbrand,
	Johannes Weiner, Lorenzo Stoakes, Matthew Wilcox (Oracle),
	Mel Gorman, Michal Hocko, Vlastimil Babka, linux-doc,
	linux-kernel, linux-mm

On Sat, Feb 11, 2023 at 07:31:18PM +0700, Bagas Sanjaya wrote:
> 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"?
 
Sure.

> -- 
> An old man doll... just what I always wanted! - Clara
> 

-- 
Sincerely yours,
Mike.


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-02-11 12:40 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-02-11 10:22 [PATCH] docs/mm: Physical Memory: add example of interleaving nodes Mike Rapoport
2023-02-11 12:31 ` Bagas Sanjaya
2023-02-11 12:39   ` Mike Rapoport

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).