From: Bharata B Rao <bharata@amd.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>,
linux-mm@kvack.org, Wei Xu <weixugc@google.com>,
Huang Ying <ying.huang@intel.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 v15 00/10] mm/demotion: Memory tiers and demotion
Date: Mon, 22 Aug 2022 09:11:18 +0530 [thread overview]
Message-ID: <537a6b8f-547b-3f12-25a7-90718a1675f3@amd.com> (raw)
In-Reply-To: <20220819173431.5c391297042eff209e821088@linux-foundation.org>
On 8/20/2022 6:04 AM, Andrew Morton wrote:
> On Fri, 19 Aug 2022 11:57:18 +0530 Bharata B Rao <bharata@amd.com> wrote:
>
>>> The kernel initialization code makes the decision on which exact tier a memory
>>> node should be assigned to based on the requests from the device drivers as well
>>> as the memory device hardware information provided by the firmware.
>>
>> I gave this patchset a quick try on two setups:
>>
>> 1. With QEMU, when an nvdimm device is bound to dax kmem driver, I can see
>> the memory node with pmem getting into a lower tier than DRAM.
>>
>> 2. In an experimental CXL setup that has DRAM as part of CXL memory, I see that
>> CXL memory node falls into the same tier as the regular DRAM tier. This is
>> expected for now since there is no code (in low level ACPI driver?) yet to
>> map the latency or bandwidth info (when available from firmware) into an
>> abstract distance value, and register a memory type for the same. Guess these
>> bits can be covered as part of future enhancements.
>
> Should I add your Tested-by:?
May be not. I have done only a very minimal testing of specific scenarios
as mentioned above. Thanks for checking.
Regards,
Bharata.
next prev parent reply other threads:[~2022-08-22 3:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-18 13:10 [PATCH v15 00/10] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 01/10] mm/demotion: Add support for explicit memory tiers Aneesh Kumar K.V
2022-08-18 13:52 ` Aneesh Kumar K V
2022-08-18 13:10 ` [PATCH v15 02/10] mm/demotion: Move memory demotion related code Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 03/10] mm/demotion: Add hotplug callbacks to handle new numa node onlined Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 04/10] mm/demotion/dax/kmem: Set node's abstract distance to MEMTIER_DEFAULT_DAX_ADISTANCE Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 05/10] mm/demotion: Build demotion targets based on explicit memory tiers Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 06/10] mm/demotion: Add pg_data_t member to track node memory tier details Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 07/10] mm/demotion: Drop memtier from memtype Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 08/10] mm/demotion: Demote pages according to allocation fallback order Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 09/10] mm/demotion: Update node_is_toptier to work with memory tiers Aneesh Kumar K.V
2022-08-18 13:10 ` [PATCH v15 10/10] lib/nodemask: Optimize node_random for nodemask with single NUMA node Aneesh Kumar K.V
2022-09-26 20:17 ` Yury Norov
2022-08-19 6:27 ` [PATCH v15 00/10] mm/demotion: Memory tiers and demotion Bharata B Rao
2022-08-20 0:34 ` Andrew Morton
2022-08-22 3:41 ` Bharata B Rao [this message]
2022-08-20 1:54 ` Wei Xu
2022-09-12 0:13 ` Andrew Morton
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=537a6b8f-547b-3f12-25a7-90718a1675f3@amd.com \
--to=bharata@amd.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 \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).