From: Andrew Morton <akpm@linux-foundation.org>
To: Huang Ying <ying.huang@intel.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>,
Alistair Popple <apopple@nvidia.com>,
Bharata B Rao <bharata@amd.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Hansen <dave.hansen@intel.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Hesham Almatary <hesham.almatary@huawei.com>,
Jagdish Gediya <jvgediya.oss@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Michal Hocko <mhocko@kernel.org>, Tim Chen <tim.c.chen@intel.com>,
Wei Xu <weixugc@google.com>, Yang Shi <shy828301@gmail.com>
Subject: Re: [PATCH] memory tier, sysfs: rename attribute "nodes" to "nodelist"
Date: Thu, 20 Oct 2022 18:47:35 -0700 [thread overview]
Message-ID: <20221020184735.aaddd0899bad4f0bb796ebde@linux-foundation.org> (raw)
In-Reply-To: <20221020015122.290097-1-ying.huang@intel.com>
On Thu, 20 Oct 2022 09:51:22 +0800 Huang Ying <ying.huang@intel.com> wrote:
> In sysfs, we use attribute name "cpumap" or "cpus" for cpu mask and
> "cpulist" or "cpus_list" for cpu list. For example, in my system,
>
> $ cat /sys/devices/system/node/node0/cpumap
> f,ffffffff
> $ cat /sys/devices/system/cpu/cpu2/topology/core_cpus
> 0,00100004
> $ cat cat /sys/devices/system/node/node0/cpulist
> 0-35
> $ cat /sys/devices/system/cpu/cpu2/topology/core_cpus_list
> 2,20
>
> It looks reasonable to use "nodemap" for node mask and "nodelist" for
> node list. So, rename the attribute to follow the naming convention.
I'll add
Fixes: 9832fb87834e2b ("mm/demotion: expose memory tier details via sysfs")
to this to reduce the risk that someone will backport 9832fb87834e2b
but will miss this alteration.
next prev parent reply other threads:[~2022-10-21 1:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:51 Huang Ying
2022-10-20 3:48 ` Wei Xu
2022-10-20 3:57 ` Aneesh Kumar K.V
2022-10-20 18:47 ` Yang Shi
2022-10-21 1:47 ` Andrew Morton [this message]
2022-10-24 19:55 ` Davidlohr Bueso
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=20221020184735.aaddd0899bad4f0bb796ebde@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--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 \
--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