From: "Huang, Ying" <ying.huang@intel.com>
To: Aneesh Kumar K V <aneesh.kumar@linux.ibm.com>
Cc: linux-mm@kvack.org, akpm@linux-foundation.org,
Wei Xu <weixugc@google.com>, Yang Shi <shy828301@gmail.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Tim C Chen <tim.c.chen@intel.com>,
Michal Hocko <mhocko@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hesham Almatary <hesham.almatary@huawei.com>,
Dave Hansen <dave.hansen@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Alistair Popple <apopple@nvidia.com>,
Dan Williams <dan.j.williams@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
jvgediya.oss@gmail.com
Subject: Re: [PATCH v13 4/9] mm/demotion/dax/kmem: Set node's abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE
Date: Wed, 10 Aug 2022 09:09:07 +0800 [thread overview]
Message-ID: <87o7wsgb0s.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <46c8d7c2-004f-1945-8614-2452d4f28d2a@linux.ibm.com> (Aneesh Kumar K. V.'s message of "Tue, 9 Aug 2022 11:03:22 +0530")
Aneesh Kumar K V <aneesh.kumar@linux.ibm.com> writes:
> On 8/9/22 8:34 AM, Huang, Ying wrote:
>> "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
>>
>>> By default, all nodes are assigned to the default memory tier which
>>> is the memory tier designated for nodes with DRAM
>>>
>>> Set dax kmem device node's tier to slower memory tier by assigning
>>> abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE. Low-level drivers
>>> like papr_scm or ACPI NFIT can initialize memory device type to a
>>> more accurate value based on device tree details or HMAT.
>>
>> I don't know how ACPI NFIT can help here. Can you teach me?
>>
>> Per my understanding, we may use the information provided by ACPI SLIT
>> or HMAT (or device tree via papr_scm) to create memory types. Before
>> that is implemented, we just create a memory type with default abstract
>> distance.
>>
>
> My idea is to use ACPI NFIT driver that creates a persistent memory region
> (nvdimm_region_create) to also create memory type and assign that to the
> NUMA node mapping that region. For now NFIT driver manages all the persistent
> memory region/DIMM creation (drivers/acpi/nfit/core.c). It can also do the
> memory type creation using other ACPI information like SLIT/HMAT etc. Similarly
> CXL driver can do the same using CDAT.
I still think that it's better to create memory types in dax/kmem.c and
CXL driver. But we can discuss further on that later.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2022-08-10 1:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 6:25 [PATCH v13 0/9] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-08-08 6:25 ` [PATCH v13 1/9] mm/demotion: Add support for explicit memory tiers Aneesh Kumar K.V
2022-08-09 1:58 ` Huang, Ying
2022-08-09 5:34 ` Aneesh Kumar K V
2022-08-08 6:25 ` [PATCH v13 2/9] mm/demotion: Move memory demotion related code Aneesh Kumar K.V
2022-08-08 6:25 ` [PATCH v13 3/9] mm/demotion: Add hotplug callbacks to handle new numa node onlined Aneesh Kumar K.V
2022-08-08 6:25 ` [PATCH v13 4/9] mm/demotion/dax/kmem: Set node's abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE Aneesh Kumar K.V
2022-08-09 3:04 ` Huang, Ying
2022-08-09 5:33 ` Aneesh Kumar K V
2022-08-10 1:09 ` Huang, Ying [this message]
2022-08-08 6:25 ` [PATCH v13 5/9] mm/demotion: Build demotion targets based on explicit memory tiers Aneesh Kumar K.V
2022-08-08 6:25 ` [PATCH v13 6/9] mm/demotion: Add pg_data_t member to track node memory tier details Aneesh Kumar K.V
2022-08-09 3:07 ` Huang, Ying
2022-08-09 5:21 ` Huang, Ying
2022-08-09 5:41 ` Aneesh Kumar K V
2022-08-10 1:03 ` Huang, Ying
2022-08-08 6:25 ` [PATCH v13 7/9] mm/demotion: Demote pages according to allocation fallback order Aneesh Kumar K.V
2022-08-08 6:26 ` [PATCH v13 8/9] mm/demotion: Update node_is_toptier to work with memory tiers Aneesh Kumar K.V
2022-08-08 6:26 ` [PATCH v13 9/9] lib/nodemask: Optimize node_random for nodemask with single NUMA node Aneesh Kumar K.V
2022-08-09 3:13 ` Huang, Ying
2022-08-09 5:43 ` Aneesh Kumar K V
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=87o7wsgb0s.fsf@yhuang6-desk2.ccr.corp.intel.com \
--to=ying.huang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=hannes@cmpxchg.org \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya.oss@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=shy828301@gmail.com \
--cc=tim.c.chen@intel.com \
--cc=weixugc@google.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