From: Tim Chen <tim.c.chen@linux.intel.com>
To: Wei Xu <weixugc@google.com>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Cc: "ying.huang@intel.com" <ying.huang@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Greg Thelen <gthelen@google.com>, Yang Shi <shy828301@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jagdish Gediya <jvgediya@linux.ibm.com>,
Michal Hocko <mhocko@kernel.org>,
Tim C Chen <tim.c.chen@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Alistair Popple <apopple@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
Feng Tang <feng.tang@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Dan Williams <dan.j.williams@intel.com>,
David Rientjes <rientjes@google.com>,
Linux MM <linux-mm@kvack.org>,
Brice Goglin <brice.goglin@gmail.com>,
Hesham Almatary <hesham.almatary@huawei.com>
Subject: Re: RFC: Memory Tiering Kernel Interfaces (v2)
Date: Thu, 12 May 2022 14:12:51 -0700 [thread overview]
Message-ID: <333438929a8680317bdae02da921d1e50fb9b0b3.camel@linux.intel.com> (raw)
In-Reply-To: <CAAPL-u90Gzrepbsdpc62FGRBYOx1LAVwZWHg1E7UyVD_CmcROw@mail.gmail.com>
On Thu, 2022-05-12 at 01:15 -0700, Wei Xu wrote:
>
> I am OK with moving back the memory tier nodelist into node/. When
> there are more memory tier attributes needed, we can then create the
> memory tier subtree and replace the tier nodelist in node/ with
> symlinks.
>
> So the revised sysfs interfaces are:
>
> * /sys/devices/system/node/memory_tierN (read-only)
>
> where N = 0, 1, 2
>
> Format: node_list
>
> * /sys/devices/system/node/nodeN/memory_tier (read/write)
>
> where N = 0, 1, ...
>
> Format: int or empty
This looks good to me. Just wonder if having just 1 tier
lower than DRAM is sufficient. We could have wide performance
range for such secondary memories and is one tier sufficient for them?
Tim
next prev parent reply other threads:[~2022-05-12 21:13 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 6:22 RFC: Memory Tiering Kernel Interfaces (v2) Wei Xu
2022-05-12 7:03 ` ying.huang
2022-05-12 7:12 ` Aneesh Kumar K V
2022-05-12 7:18 ` ying.huang
2022-05-12 7:22 ` Wei Xu
2022-05-12 7:36 ` Aneesh Kumar K.V
2022-05-12 8:15 ` Wei Xu
2022-05-12 8:37 ` ying.huang
2022-05-13 2:52 ` ying.huang
2022-05-13 7:00 ` Wei Xu
2022-05-16 1:57 ` ying.huang
2022-05-12 21:12 ` Tim Chen [this message]
2022-05-12 21:31 ` Wei Xu
2022-05-12 15:00 ` Jonathan Cameron
2022-05-18 7:09 ` Wei Xu
2022-05-18 12:00 ` Jonathan Cameron
2022-05-24 7:36 ` Wei Xu
2022-05-24 13:26 ` Aneesh Kumar K.V
2022-05-25 5:27 ` Wei Xu
2022-05-25 7:47 ` Alistair Popple
2022-05-25 11:48 ` Jonathan Cameron
2022-05-25 15:32 ` Wei Xu
2022-05-20 3:06 ` Ying Huang
2022-05-24 7:04 ` Wei Xu
2022-05-24 8:24 ` Ying Huang
2022-05-25 5:32 ` Wei Xu
2022-05-25 9:03 ` Ying Huang
2022-05-25 10:01 ` Aneesh Kumar K V
2022-05-25 11:36 ` Mika Penttilä
2022-05-25 15:33 ` Wei Xu
2022-05-25 17:27 ` Wei Xu
2022-05-26 9:32 ` Jonathan Cameron
2022-05-26 20:30 ` Wei Xu
2022-05-27 9:26 ` Aneesh Kumar K V
2022-05-25 15:36 ` Wei Xu
2022-05-26 1:09 ` Ying Huang
2022-05-26 3:53 ` Wei Xu
2022-05-26 6:54 ` Ying Huang
2022-05-26 7:08 ` Wei Xu
2022-05-26 7:39 ` Ying Huang
2022-05-26 20:55 ` Wei Xu
2022-05-27 9:10 ` Jonathan Cameron
2022-05-30 6:54 ` Ying Huang
2022-05-13 3:25 ` ying.huang
2022-05-13 6:36 ` Wei Xu
2022-05-13 7:04 ` ying.huang
2022-05-13 7:21 ` Wei Xu
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=333438929a8680317bdae02da921d1e50fb9b0b3.camel@linux.intel.com \
--to=tim.c.chen@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=apopple@nvidia.com \
--cc=baolin.wang@linux.alibaba.com \
--cc=brice.goglin@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=feng.tang@intel.com \
--cc=gthelen@google.com \
--cc=hesham.almatary@huawei.com \
--cc=jvgediya@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--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).