From: Waiman Long <longman@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Jonathan Corbet <corbet@lwn.net>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Shuah Khan <shuah@kernel.org>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH-cgroup 3/4] cgroup/cpuset: Keep track of CPUs in isolated partitions
Date: Wed, 18 Oct 2023 09:30:04 -0400 [thread overview]
Message-ID: <9e2772e3-f615-5e80-6922-5a2dd06a8b07@redhat.com> (raw)
In-Reply-To: <ZS-kt6X5Dd1lktAw@slm.duckdns.org>
On 10/18/23 05:26, Tejun Heo wrote:
> On Fri, Oct 13, 2023 at 02:11:21PM -0400, Waiman Long wrote:
> ...
>> @@ -3875,6 +3931,13 @@ static struct cftype dfl_files[] = {
>> .flags = CFTYPE_ONLY_ON_ROOT | CFTYPE_DEBUG,
>> },
>>
>> + {
>> + .name = "cpus.isolated",
>> + .seq_show = cpuset_common_seq_show,
>> + .private = FILE_ISOLATED_CPULIST,
>> + .flags = CFTYPE_ONLY_ON_ROOT | CFTYPE_DEBUG,
>> + },
> I'd much rather show this in a wq sysfs file along with other related masks,
> and not in a DEBUG file.
It can certainly be exposed as a permanent addition to the cgroup
control files instead of a debug only file. However this set of isolated
CPUs may be used by others not just by workqueue. So I doubt if it
should be a sysfs file in the workqueue directory. I can see if it is
possible to put a symlink there point back to the cgroupfs.
Thanks,
Longman
next prev parent reply other threads:[~2023-10-18 13:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 18:11 [PATCH-cgroup 0/4] cgroup/cpuset: Improve CPU isolation " Waiman Long
2023-10-13 18:11 ` [PATCH-cgroup 1/4] workqueue: Add workqueue_unbound_exclude_cpumask() to exclude CPUs from wq_unbound_cpumask Waiman Long
2023-10-18 9:24 ` Tejun Heo
2023-10-18 13:41 ` Waiman Long
2023-10-18 19:18 ` Waiman Long
2023-10-24 3:28 ` Tejun Heo
2023-10-25 18:47 ` Waiman Long
2023-10-13 18:11 ` [PATCH-cgroup 2/4] selftests/cgroup: Minor code cleanup and reorganization of test_cpuset_prs.sh Waiman Long
2023-10-13 18:11 ` [PATCH-cgroup 3/4] cgroup/cpuset: Keep track of CPUs in isolated partitions Waiman Long
2023-10-18 9:26 ` Tejun Heo
2023-10-18 13:30 ` Waiman Long [this message]
2023-10-18 18:08 ` Tejun Heo
2023-10-18 18:24 ` Waiman Long
2023-10-24 3:25 ` Tejun Heo
2023-10-25 18:46 ` Waiman Long
2023-10-13 18:11 ` [PATCH-cgroup 4/4] cgroup/cpuset: Take isolated CPUs out of workqueue unbound cpumask 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=9e2772e3-f615-5e80-6922-5a2dd06a8b07@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=shuah@kernel.org \
--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®