From: Akinobu Mita <akinobu.mita@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, hannes@cmpxchg.org,
david@kernel.org, mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, vbabka@suse.cz, rppt@kernel.org,
surenb@google.com
Subject: Re: [PATCH 1/2] mm: memory-tiers, numa_emu: enable to create memory tiers using fake numa nodes
Date: Wed, 17 Dec 2025 22:55:16 +0900 [thread overview]
Message-ID: <CAC5umyjCXSm1TMiv+OOdK1vHp5nA7zGRxLegMzhbLd9U=3Dbhg@mail.gmail.com> (raw)
In-Reply-To: <20251216122441.2810043bbc51621315e3862c@linux-foundation.org>
2025年12月17日(水) 5:24 Andrew Morton <akpm@linux-foundation.org>:
>
> On Mon, 8 Dec 2025 18:40:27 +0900 Akinobu Mita <akinobu.mita@gmail.com> wrote:
>
> > This makes it possible to create memory tiers using fake numa nodes
> > generated by numa emulation.
> >
> > The new "numa_emulation.adistance" kernel parameter allows you to set the
> > abstract distance for each NUMA node.
> >
> > For example, if the system is booted with the parameters
> > "numa=fake=2 numa_emulation.adistance=576,704", it will configure memory
> > tiers with node0 having the default DRAM adistance value and node1 having
> > a lower adistance value.
>
> Confusing. I'd have thought that this commandline would gave node0 a
> distance of 576 and node1 a distance of 704? But the text talks about
> some third "default" distance, of unknown value.
>
> Can we please clear all this up?
The DRAM abstract distance is defined by MEMTIER_ADISTANCE_DRAM
in linux/memory-tiers.h and has a value of 576.
Each memory tier covers an abstract distance chunk size of 128,
so nodes with abstract distances between 512 and 639 are classified
into the DRAM tier.
Here, the abstract distances of node0 and node1 are set to 576 and 706,
respectively, so they are classified into different tiers.
> Also, we have little documentation for this stuff.
> fake-numa-for-cpusets.rst and kernel-parameters.txt. Can you please
> find somewhere appropriate to document this new user-facing feature?
> Maybe a new Documentation file?
Looks good.
I'll create a new Documentation/mm/numa_emulation.rst and
document at least this new parameter.
next prev parent reply other threads:[~2025-12-17 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-08 9:40 [PATCH 0/2] mm: fix oom-killer not being invoked when demotion is enabled Akinobu Mita
2025-12-08 9:40 ` [PATCH 1/2] mm: memory-tiers, numa_emu: enable to create memory tiers using fake numa nodes Akinobu Mita
2025-12-16 20:24 ` Andrew Morton
2025-12-17 13:55 ` Akinobu Mita [this message]
2025-12-08 9:40 ` [PATCH 2/2] mm/vmscan: don't demote if there is not enough free memory in the lower memory tier Akinobu Mita
2025-12-17 12:55 ` Vlastimil Babka
2025-12-17 14:30 ` Akinobu Mita
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='CAC5umyjCXSm1TMiv+OOdK1vHp5nA7zGRxLegMzhbLd9U=3Dbhg@mail.gmail.com' \
--to=akinobu.mita@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@kernel.org \
--cc=rppt@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.com \
/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