From: "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
To: linux-mm@kvack.org, akpm@linux-foundation.org
Cc: 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>,
"Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com>
Subject: [PATCH v7 12/12] mm/demotion: Add sysfs ABI documentation
Date: Wed, 22 Jun 2022 13:55:13 +0530 [thread overview]
Message-ID: <20220622082513.467538-13-aneesh.kumar@linux.ibm.com> (raw)
In-Reply-To: <20220622082513.467538-1-aneesh.kumar@linux.ibm.com>
Add sysfs ABI documentation.
Signed-off-by: Wei Xu <weixugc@google.com>
Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
---
.../ABI/testing/sysfs-kernel-mm-memory-tiers | 61 +++++++++++++++++++
1 file changed, 61 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-kernel-mm-memory-tiers
diff --git a/Documentation/ABI/testing/sysfs-kernel-mm-memory-tiers b/Documentation/ABI/testing/sysfs-kernel-mm-memory-tiers
new file mode 100644
index 000000000000..843fb59d2f3d
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-kernel-mm-memory-tiers
@@ -0,0 +1,61 @@
+What: /sys/devices/system/memtier/
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Interface for tiered memory
+
+ This is the directory containing the information about memory tiers.
+
+ Each memory tier has its own subdirectory.
+
+ The order of memory tiers is determined by their tier ID value.
+ A higher tier ID value means a higher tier. memtier300 is higher
+ memory tier compared to memtier 100.
+
+What: /sys/devices/system/memtier/default_tier
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Default memory tier
+
+ The default memory tier to which memory would get added via hotplug
+ if the NUMA node is not part of any memory tier
+
+What: /sys/devices/system/memtier/max_tier
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Maximum memory tier ID supported
+
+ The max memory tier device ID we can create. Users can create memory
+ tiers in range [0 - max_tier]
+
+What: /sys/devices/system/memtier/memtierN/
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Directory with details of a specific memory tier
+
+ This is the directory containing the information about a particular
+ memory tier, memtierN, where N is the memtier device ID (e.g. 0, 1).
+
+ The memtier device ID number itself is just an identifier and has no
+ special meaning. Its value relative to other memtiers decides the level
+ of this memtier in the tier hierarchy.
+
+
+What: /sys/devices/system/memtier/memtierN/nodelist
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Memory tier nodelist
+
+
+ When read, list the memory nodes in the specified tier.
+
+What: /sys/devices/system/node/nodeN/memtier
+Date: June 2022
+Contact: Linux memory management mailing list <linux-mm@kvack.org>
+Description: Memory tier details for node N
+
+ When read, list the device ID of the memory tier that the node belongs
+ to. Its value is empty for a CPU-only NUMA node.
+
+ When written, the kernel moves the node into the specified memory
+ tier if the move is allowed. The tier assignments of all other
+ nodes are not affected.
--
2.36.1
next prev parent reply other threads:[~2022-06-22 8:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 8:25 [PATCH v7 00/12] mm/demotion: Memory tiers and demotion Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 01/12] mm/demotion: Add support for explicit memory tiers Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 02/12] mm/demotion: Move memory demotion related code Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 03/12] mm/demotion/dax/kmem: Set node's memory tier to MEMORY_TIER_PMEM Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 04/12] mm/demotion: Add hotplug callbacks to handle new numa node onlined Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 05/12] mm/demotion: Build demotion targets based on explicit memory tiers Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 06/12] mm/demotion: Expose memory tier details via sysfs Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 07/12] mm/demotion: Add per node memory tier attribute to sysfs Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 08/12] mm/demotion: Add pg_data_t member to track node memory tier details Aneesh Kumar K.V
2022-06-22 22:52 ` kernel test robot
2022-06-22 8:25 ` [PATCH v7 09/12] mm/demotion: Demote pages according to allocation fallback order Aneesh Kumar K.V
2022-06-23 2:53 ` Alistair Popple
2022-06-27 3:54 ` Aneesh Kumar K.V
2022-06-27 4:18 ` Alistair Popple
2022-06-22 8:25 ` [PATCH v7 10/12] mm/demotion: Update node_is_toptier to work with memory tiers Aneesh Kumar K.V
2022-06-22 8:25 ` [PATCH v7 11/12] mm/demotion: Add documentation for memory tiering Aneesh Kumar K.V
2022-06-22 21:21 ` kernel test robot
2022-06-25 2:56 ` Bagas Sanjaya
2022-06-25 4:13 ` Bagas Sanjaya
2022-06-27 4:40 ` Aneesh Kumar K.V
2022-06-30 0:57 ` Souptick Joarder
2022-06-22 8:25 ` Aneesh Kumar K.V [this message]
2022-06-22 11:06 ` [PATCH v7 00/12] mm/demotion: Memory tiers and demotion 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=20220622082513.467538-13-aneesh.kumar@linux.ibm.com \
--to=aneesh.kumar@linux.ibm.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=dave@stgolabs.net \
--cc=hesham.almatary@huawei.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).