From: Oscar Salvador <osalvador@suse.de>
To: Xiu Jianfeng <xiujianfeng@huawei.com>
Cc: akpm@linux-foundation.org, muchun.song@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 -next 1/3] mm/hugetlb_cgroup: identify the legacy using cgroup_subsys_on_dfl()
Date: Mon, 10 Jun 2024 07:03:46 +0200 [thread overview]
Message-ID: <ZmaJMqqc4myJNUEm@localhost.localdomain> (raw)
In-Reply-To: <20240605070133.1941677-2-xiujianfeng@huawei.com>
On Wed, Jun 05, 2024 at 07:01:31AM +0000, Xiu Jianfeng wrote:
> Currently the numa_stat file encodes 1 into private using the micro
> MEMFILE_PRIVATE() to identify the legacy. Actually, we can use
> cgroup_subsys_on_dfl() instead. This is helpful to handle .private
> in the static array of the comming patch.
>
> Signed-off-by: Xiu Jianfeng <xiujianfeng@huawei.com>
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Nit below:
> ---
> mm/hugetlb_cgroup.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/mm/hugetlb_cgroup.c b/mm/hugetlb_cgroup.c
> index e20339a346b9..45f94a869776 100644
> --- a/mm/hugetlb_cgroup.c
> +++ b/mm/hugetlb_cgroup.c
> @@ -460,7 +460,7 @@ static int hugetlb_cgroup_read_numa_stat(struct seq_file *seq, void *dummy)
> int nid;
> struct cftype *cft = seq_cft(seq);
> int idx = MEMFILE_IDX(cft->private);
> - bool legacy = MEMFILE_ATTR(cft->private);
> + bool legacy = !cgroup_subsys_on_dfl(hugetlb_cgrp_subsys);
> struct hugetlb_cgroup *h_cg = hugetlb_cgroup_from_css(seq_css(seq));
> struct cgroup_subsys_state *css;
> unsigned long usage;
> @@ -839,7 +839,7 @@ static void __init __hugetlb_cgroup_file_legacy_init(int idx)
> /* Add the numa stat file */
> cft = &h->cgroup_files_legacy[8];
> snprintf(cft->name, MAX_CFTYPE_NAME, "%s.numa_stat", buf);
> - cft->private = MEMFILE_PRIVATE(idx, 1);
> + cft->private = MEMFILE_PRIVATE(idx, 0);
Do we still have to set it to '0'?
Is it not by default?
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-06-10 5:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 7:01 [PATCH v2 -next 0/3] mm/hugetlb_cgroup: rework on cftypes Xiu Jianfeng
2024-06-05 7:01 ` [PATCH v2 -next 1/3] mm/hugetlb_cgroup: identify the legacy using cgroup_subsys_on_dfl() Xiu Jianfeng
2024-06-10 5:03 ` Oscar Salvador [this message]
2024-06-11 2:28 ` xiujianfeng
2024-06-05 7:01 ` [PATCH v2 -next 2/3] mm/hugetlb_cgroup: prepare cftypes based on template Xiu Jianfeng
2024-06-11 2:29 ` xiujianfeng
2024-06-05 7:01 ` [PATCH v2 -next 3/3] mm/hugetlb_cgroup: switch to the new cftypes Xiu Jianfeng
2024-06-07 7:42 ` [PATCH v2 -next 0/3] mm/hugetlb_cgroup: rework on cftypes Oscar Salvador
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=ZmaJMqqc4myJNUEm@localhost.localdomain \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=xiujianfeng@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.