From: Waiman Long <longman@redhat.com>
To: "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
Juri Lelli <juri.lelli@redhat.com>,
Waiman Long <longman@redhat.com>
Subject: [PATCH 0/3] cgroup/cpuset: Remove redundant rebuild_sched_domains_locked() calls
Date: Sat, 9 Nov 2024 21:50:20 -0500 [thread overview]
Message-ID: <20241110025023.664487-1-longman@redhat.com> (raw)
The main purpose of this series is to make sure that there will
be at most one rebuild_sched_domains_locked() call per cpuset
operation. Juri found that is still not the case. Make use of the
existing cpuset_force_rebuild() helper as a replacement for a direct
rebuild_sched_domains_locked() call and check force_sd_rebuild at the
operation end.
The last patch is for removing some unnecessary v1 specific code if
CONFIG_CPUSETS_V1 isn't set.
Waiman Long (3):
cgroup/cpuset: Revert "Allow suppression of sched domain rebuild in
update_cpumasks_hier()"
cgroup/cpuset: Enforce at most one rebuild_sched_domains_locked() call
per operation
cgroup/cpuset: Further optimize code if CONFIG_CPUSETS_V1 not set
kernel/cgroup/cpuset.c | 121 +++++++++++++++++++++--------------------
1 file changed, 63 insertions(+), 58 deletions(-)
--
2.47.0
next reply other threads:[~2024-11-10 2:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-10 2:50 Waiman Long [this message]
2024-11-10 2:50 ` [PATCH 1/3] cgroup/cpuset: Revert "Allow suppression of sched domain rebuild in update_cpumasks_hier()" Waiman Long
2024-11-10 2:50 ` [PATCH 2/3] cgroup/cpuset: Enforce at most one rebuild_sched_domains_locked() call per operation Waiman Long
2024-11-11 10:56 ` Juri Lelli
2024-11-10 2:50 ` [PATCH 3/3] cgroup/cpuset: Further optimize code if CONFIG_CPUSETS_V1 not set Waiman Long
2024-11-12 19:08 ` [PATCH 0/3] cgroup/cpuset: Remove redundant rebuild_sched_domains_locked() calls 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=20241110025023.664487-1-longman@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkoutny@suse.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
all inboxes | Powered by JetHome®