All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Waiman Long <llong@redhat.com>,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
	Johannes Weiner <hannes@cmpxchg.org>,
	Chen Ridong <chenridong@huawei.com>
Subject: Re: [PATCH] cgroup/cpuset: Move procfs cpuset attribute under cgroup-v1.c
Date: Thu, 16 Jan 2025 07:25:03 -1000	[thread overview]
Message-ID: <Z4lA702nBSWNFQYm@slm.duckdns.org> (raw)
In-Reply-To: <l7o4dygoe2h7koumizjqljs7meqs4dzngkw6ugypgk6smqdqbm@ocl4ldt5izmr>

Hello,

On Thu, Jan 16, 2025 at 03:05:32PM +0100, Michal Koutný wrote:
> On Thu, Jan 16, 2025 at 08:40:56AM -0500, Waiman Long <llong@redhat.com> wrote:
> > I do have some reservation in taking out /proc/<pid>/cpuset by default as
> > CPUSETS_V1 is off by default. This may break some existing user scripts.
> 
> Cannot be /proc/$pid/cpuset declared a v1 feature?
> Similar to cpuset fs (that is under CPUSETS_V1). If there's a breakage,
> the user is not non-v1 ready and CPUSETS_V1 must be enabled.

I think we can try given that the config is providing an exit path. After
all, users who were depending on cpusets on v1 are in the same boat.

Thanks.

-- 
tejun

  reply	other threads:[~2025-01-16 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-16  9:56 [PATCH] cgroup/cpuset: Move procfs cpuset attribute under cgroup-v1.c Michal Koutný
2025-01-16 13:40 ` Waiman Long
2025-01-16 14:05   ` Michal Koutný
2025-01-16 17:25     ` Tejun Heo [this message]
2025-01-16 19:15       ` Waiman Long
2025-01-16 19:38         ` Tejun Heo
2025-01-17 10:44           ` [PATCH v2] " Michal Koutný
2025-01-17 14:39             ` Waiman Long
2025-01-17 16:08             ` Tejun Heo

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=Z4lA702nBSWNFQYm@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huawei.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llong@redhat.com \
    --cc=mkoutny@suse.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.