mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: "Michal Koutný" <mkoutny@suse.com>,
	cgroups@vger.kernel.org, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Josef Bacik <josef@toxicpanda.com>,
	Jens Axboe <axboe@kernel.dk>,
	Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH 1/9] cgroup/cpuset-v1: Add deprecation warnings to sched_load_balance and memory_pressure_enabled
Date: Tue, 4 Mar 2025 11:19:00 -0500	[thread overview]
Message-ID: <8b8f0f99-6d42-4c6f-9c43-d0224bdedf9e@redhat.com> (raw)
In-Reply-To: <20250304153801.597907-2-mkoutny@suse.com>


On 3/4/25 10:37 AM, Michal Koutný wrote:
> These two v1 feature have analogues in cgroup v2.
>
> Signed-off-by: Michal Koutný <mkoutny@suse.com>
> ---
>   kernel/cgroup/cpuset-v1.c | 2 ++
>   1 file changed, 2 insertions(+)
>
> diff --git a/kernel/cgroup/cpuset-v1.c b/kernel/cgroup/cpuset-v1.c
> index 25c1d7b77e2f2..3e81ac76578c7 100644
> --- a/kernel/cgroup/cpuset-v1.c
> +++ b/kernel/cgroup/cpuset-v1.c
> @@ -430,12 +430,14 @@ static int cpuset_write_u64(struct cgroup_subsys_state *css, struct cftype *cft,
>   		retval = cpuset_update_flag(CS_MEM_HARDWALL, cs, val);
>   		break;
>   	case FILE_SCHED_LOAD_BALANCE:
> +		pr_warn_once("cpuset.%s is deprecated, use cpus.partition instead\n", cft->name);
Should you use the full name "cpuset.cpus.partition" instead?
>   		retval = cpuset_update_flag(CS_SCHED_LOAD_BALANCE, cs, val);
>   		break;
>   	case FILE_MEMORY_MIGRATE:
>   		retval = cpuset_update_flag(CS_MEMORY_MIGRATE, cs, val);
>   		break;
>   	case FILE_MEMORY_PRESSURE_ENABLED:
> +		pr_warn_once("cpuset.%s is deprecated, use memory.pressure instead\n", cft->name);

memory.pressure depends on CONFIG_PSI, so it may not available in some 
cases. My suggestion is to add a "if available" suffix.

I do have some concern with the use of pr_warn*() because some users may 
attempt to use the panic_on_warn command line option.

Cheers,
Longman


  reply	other threads:[~2025-03-04 16:19 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 15:37 [PATCH 0/9] cgroup v1 deprecation warnings Michal Koutný
2025-03-04 15:37 ` [PATCH 1/9] cgroup/cpuset-v1: Add deprecation warnings to sched_load_balance and memory_pressure_enabled Michal Koutný
2025-03-04 16:19   ` Waiman Long [this message]
2025-03-04 16:52     ` Tejun Heo
2025-03-04 17:10       ` Michal Koutný
2025-03-04 17:33         ` Waiman Long
2025-03-04 18:04           ` Tejun Heo
2025-03-05 10:12             ` Michal Koutný
2025-03-05 18:39               ` Tejun Heo
2025-03-04 15:37 ` [PATCH 2/9] cgroup/cpuset-v1: Add deprecation warnings to memory_spread_page and memory_spread_slab Michal Koutný
2025-03-04 15:37 ` [PATCH 3/9] cgroup/blkio: Add deprecation warnings to reset_stats Michal Koutný
2025-03-04 15:37 ` [PATCH 4/9] cgroup: Print warning when /proc/cgroups is read on v2-only system Michal Koutný
2025-03-04 16:55   ` Tejun Heo
2025-03-05 10:17     ` Michal Koutný
2025-03-05 16:27       ` Waiman Long
2025-03-04 15:37 ` [PATCH 5/9] RFC cgroup/cpuset-v1: Add deprecation warnings to mem_exclusive and mem_hardwall Michal Koutný
2025-03-04 15:37 ` [PATCH 6/9] RFC cgroup/cpuset-v1: Add deprecation warnings to memory_migrate Michal Koutný
2025-03-04 15:37 ` [PATCH 7/9] RFC cgroup/cpuset-v1: Add deprecation warnings to sched_relax_domain_level Michal Koutný
2025-03-04 15:38 ` [PATCH 8/9] cgroup: Update file naming comment Michal Koutný
2025-03-04 15:38 ` [PATCH 9/9] blk-cgroup: Simplify policy files registration Michal Koutný

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=8b8f0f99-6d42-4c6f-9c43-d0224bdedf9e@redhat.com \
    --to=llong@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=tj@kernel.org \
    /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

all inboxes | Powered by JetHome®