LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Tejun Heo <email@example.com> To: Waiman Long <firstname.lastname@example.org> Cc: "Zefan Li" <email@example.com>, "Johannes Weiner" <firstname.lastname@example.org>, "Jonathan Corbet" <email@example.com>, "Shuah Khan" <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, "Andrew Morton" <email@example.com>, "Roman Gushchin" <firstname.lastname@example.org>, "Phil Auld" <email@example.com>, "Peter Zijlstra" <firstname.lastname@example.org>, "Juri Lelli" <email@example.com>, "Frederic Weisbecker" <firstname.lastname@example.org>, "Marcelo Tosatti" <email@example.com>, "Michal Koutný" <firstname.lastname@example.org> Subject: Re: [PATCH v4 2/6] cgroup/cpuset: Properly handle partition root tree Date: Thu, 12 Aug 2021 12:18:40 -1000 [thread overview] Message-ID: <YRWeQH6gY5PqIanD@slm.duckdns.org> (raw) In-Reply-To: <email@example.com> Hello, On Wed, Aug 11, 2021 at 03:27:20PM -0400, Waiman Long wrote: > Disabling partition at the parent level does invalidate all the child > partitions under it. So it must be done with care when we disable a > partition. > > How about we give some indication that a child partition exist when reading > cpuset.cpus.partition and recommend double-checking it before disabling a > partition? For example, we keep track of the number of cpus delegated to > child partitions. Perhaps we can list that information on read. > > With that information available, I have no objection to allow disabling a > parent partition with child partitions under it. This is a general problem which has always existed regardless of whether the errors are synchronous or not. There are many different reasons that a write to a cpuset interface file could fail and it has never been easy to tell why a given operation was rejected. Making error notifications asynchronous doesn't really change anything fundamental although it does make the situation a bit more opaque. I'm all for improving visibility. Now that we can consolidate most error states into a unified failure state, this might actually be easier to do. IOW, we now just have to explain why a given cgroup is in an invalid state rather than additionally having to explain why a given write has been rejected, which is pretty awkward to do as those failures are transient and local to the writer. So, if you wanna tackle this, let's do it right and provide something comprehensive rather than explaining just one failure. Thanks. -- tejun
next prev parent reply other threads:[~2021-08-12 22:18 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-11 3:06 [PATCH-cgroup v4 0/6] cgroup/cpuset: Add new cpuset partition type & empty effecitve cpus Waiman Long 2021-08-11 3:06 ` [PATCH v4 1/6] cgroup/cpuset: Enable event notification when partition state changes Waiman Long 2021-08-11 18:04 ` Tejun Heo 2021-08-11 3:06 ` [PATCH v4 2/6] cgroup/cpuset: Properly handle partition root tree Waiman Long 2021-08-11 18:08 ` Tejun Heo 2021-08-11 19:27 ` Waiman Long 2021-08-12 22:18 ` Tejun Heo [this message] 2021-08-12 22:56 ` Waiman Long 2021-08-13 16:07 ` Tejun Heo 2021-08-11 3:06 ` [PATCH v4 3/6] cgroup/cpuset: Add a new isolated cpus.partition type Waiman Long 2021-08-11 3:06 ` [PATCH v4 4/6] cgroup/cpuset: Allow non-top parent partition root to distribute out all CPUs Waiman Long 2021-08-11 18:13 ` Tejun Heo 2021-08-11 18:18 ` Waiman Long 2021-08-11 18:21 ` Tejun Heo 2021-08-11 18:46 ` Waiman Long 2021-08-12 21:51 ` Tejun Heo 2021-08-11 3:06 ` [PATCH v4 5/6] cgroup/cpuset: Update description of cpuset.cpus.partition in cgroup-v2.rst Waiman Long 2021-08-11 18:15 ` Tejun Heo 2021-08-11 18:19 ` Waiman Long 2021-08-11 3:06 ` [PATCH v4 6/6] kselftest/cgroup: Add cpuset v2 partition root state test Waiman Long
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=YRWeQH6gY5PqIanD@slm.duckdns.org \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.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: linkBe 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; as well as URLs for NNTP newsgroup(s).