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, Bharata B Rao <bharata@amd.com>
Subject: Re: [PATCH v4] mm/demotion: Expose memory tier details via sysfs
Date: Mon, 26 Sep 2022 09:04:16 +0800 [thread overview]
Message-ID: <87zgenhrov.fsf@yhuang6-desk2.ccr.corp.intel.com> (raw)
In-Reply-To: <3a966604-77c5-e6fc-1541-2fed7c71cc0c@linux.ibm.com> (Aneesh Kumar K. V.'s message of "Fri, 23 Sep 2022 16:05:30 +0530")
Aneesh Kumar K V <aneesh.kumar@linux.ibm.com> writes:
> On 9/23/22 1:37 PM, Huang, Ying wrote:
>> "Aneesh Kumar K.V" <aneesh.kumar@linux.ibm.com> writes:
>>
>>> This patch adds /sys/devices/virtual/memory_tiering/ where all memory tier
>>> related details can be found. All allocated memory tiers will be listed
>>> there as /sys/devices/virtual/memory_tiering/memory_tierN/
>>>
>>> The nodes which are part of a specific memory tier can be listed via
>>> /sys/devices/virtual/memory_tiering/memory_tierN/nodes
>>
>> It appears that XXXs is used for mask while XXXs_list is used for list?
>> For example,
>>
>> # cat /sys/devices/system/cpu/cpu2/topology/core_cpus
>> 0,00100004
>> # cat /sys/devices/system/cpu/cpu2/topology/core_cpus_list
>> 2,20
>>
>> It's better to follow the this convention?
>>
>
> That is not followed in other parts of the kernel. I was loking at cpuset
>
> $cat cpuset.cpus.effective
> 0-7
Per my understanding, cpuset isn't sysfs, but cgroupfs?
I did some research in my system,
$ grep . $(find /sys/devices | grep 'list$')
and
$ grep . $(find /sys/devices | grep 'cpus$')
I found that the cpus/cpus_list convention is used in
- pci
/sys/devices/pci0000:64/0000:64:0d.2/local_cpulist:0-35
/sys/devices/pci0000:64/0000:64:0c.2/local_cpus:f,ffffffff
- system
/sys/devices/system/cpu/cpu7/topology/core_cpus_list:7,25
/sys/devices/system/cpu/cpu7/topology/core_cpus:0,02000080
- block
/sys/devices/virtual/block/loop1/mq/0/cpu_list:0, 1, 2, ...
- net
/sys/devices/virtual/net/lo/queues/rx-0/rps_cpus:0,00000000
And I haven't found any exception in sysfs of my system. Can you find
some?
Best Regards,
Huang, Ying
>>> A directory hierarchy looks like
>>> :/sys/devices/virtual/memory_tiering$ tree memory_tier4/
>>> memory_tier4/
>>> ├── nodes
>>> ├── subsystem -> ../../../../bus/memory_tiering
>>> └── uevent
>>>
>>> :/sys/devices/virtual/memory_tiering$ cat memory_tier4/nodes
>>> 0,2
>>>
>>> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
>>
>> Best Regards,
>> Huang, Ying
>>
>> [snip]
prev parent reply other threads:[~2022-09-26 1:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 10:22 [PATCH v4] mm/demotion: Expose memory tier details via sysfs Aneesh Kumar K.V
2022-09-23 8:07 ` Huang, Ying
2022-09-23 10:35 ` Aneesh Kumar K V
2022-09-26 1:04 ` Huang, Ying [this message]
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=87zgenhrov.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=bharata@amd.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;
as well as URLs for NNTP newsgroup(s).