From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
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,
Peter Hunt <pehunt@redhat.com>,
Frederic Weisbecker <frederic@kernel.org>
Subject: Re: [PATCH v2 0/4] cgroup/cpuset: Improve CPU isolation in isolated partitions
Date: Sun, 12 Nov 2023 15:10:59 -0600 [thread overview]
Message-ID: <ZVE_YwujdpcFDbGy@mtj.duckdns.org> (raw)
In-Reply-To: <20231025182555.4155614-1-longman@redhat.com>
On Wed, Oct 25, 2023 at 02:25:51PM -0400, Waiman Long wrote:
> v2:
> - Add 2 read-only workqueue sysfs files to expose the user requested
> cpumask as well as the isolated CPUs to be excluded from
> wq_unbound_cpumask.
> - Ensure that caller of the new workqueue_unbound_exclude_cpumask()
> hold cpus_read_lock.
> - Update the cpuset code to make sure the cpus_read_lock is held
> whenever workqueue_unbound_exclude_cpumask() may be called.
Applied to cgroup/for-6.8 with patch description for the third patch updated
to reflect the dropping of __DEBUG__ prefix.
Thanks.
--
tejun
prev parent reply other threads:[~2023-11-12 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 18:25 [PATCH v2 0/4] cgroup/cpuset: Improve CPU isolation in isolated partitions Waiman Long
2023-10-25 18:25 ` [PATCH v2 1/4] workqueue: Add workqueue_unbound_exclude_cpumask() to exclude CPUs from wq_unbound_cpumask Waiman Long
2023-10-25 18:25 ` [PATCH v2 2/4] selftests/cgroup: Minor code cleanup and reorganization of test_cpuset_prs.sh Waiman Long
2023-10-25 18:25 ` [PATCH v2 3/4] cgroup/cpuset: Keep track of CPUs in isolated partitions Waiman Long
2023-10-25 18:25 ` [PATCH v2 4/4] cgroup/cpuset: Take isolated CPUs out of workqueue unbound cpumask Waiman Long
2023-11-09 9:02 ` [PATCH v2 0/4] cgroup/cpuset: Improve CPU isolation in isolated partitions Zhang, Rui
2023-11-10 1:24 ` Waiman Long
2023-11-12 21:10 ` Tejun Heo [this message]
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=ZVE_YwujdpcFDbGy@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=frederic@kernel.org \
--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=longman@redhat.com \
--cc=pehunt@redhat.com \
--cc=shuah@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 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.