public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: 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>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Waiman Long" <longman@redhat.com>, "Paul Jackson" <pj@sgi.com>
Subject: [PATCH 6/9] RFC cgroup/cpuset-v1: Add deprecation warnings to memory_migrate
Date: Tue,  4 Mar 2025 16:37:58 +0100	[thread overview]
Message-ID: <20250304153801.597907-7-mkoutny@suse.com> (raw)
In-Reply-To: <20250304153801.597907-1-mkoutny@suse.com>

Memory migration (between cgroups) was given up in v2 due to performance
reasons of its implementation. Migration between NUMA nodes within one
memcg may still make sense to modify affinity at runtime though.

Cc: Paul Jackson <pj@sgi.com>
Signed-off-by: Michal Koutný <mkoutny@suse.com>
---
 kernel/cgroup/cpuset-v1.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/kernel/cgroup/cpuset-v1.c b/kernel/cgroup/cpuset-v1.c
index 05d3622ea41e5..6155d890f10a4 100644
--- a/kernel/cgroup/cpuset-v1.c
+++ b/kernel/cgroup/cpuset-v1.c
@@ -436,6 +436,7 @@ static int cpuset_write_u64(struct cgroup_subsys_state *css, struct cftype *cft,
 		retval = cpuset_update_flag(CS_SCHED_LOAD_BALANCE, cs, val);
 		break;
 	case FILE_MEMORY_MIGRATE:
+		pr_warn_once("cpuset.%s is deprecated\n", cft->name);
 		retval = cpuset_update_flag(CS_MEMORY_MIGRATE, cs, val);
 		break;
 	case FILE_MEMORY_PRESSURE_ENABLED:
-- 
2.48.1


  parent reply	other threads:[~2025-03-04 15:38 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
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 ` Michal Koutný [this message]
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=20250304153801.597907-7-mkoutny@suse.com \
    --to=mkoutny@suse.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=longman@redhat.com \
    --cc=pj@sgi.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