From: Tejun Heo <tj@kernel.org>
To: Waiman Long <longman@redhat.com>
Cc: Zefan Li <lizefan.x@bytedance.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
kernel-team@android.com
Subject: Re: [PATCH v2 0/2] cgroup/cpuset: Make hotplug code more efficient
Date: Thu, 2 Feb 2023 11:52:46 -1000 [thread overview]
Message-ID: <Y9wwrvRDCspI6fhT@slm.duckdns.org> (raw)
In-Reply-To: <20230202143200.128753-1-longman@redhat.com>
On Thu, Feb 02, 2023 at 09:31:58AM -0500, Waiman Long wrote:
> v2:
> - It turns out it works around the v1 cpuset missing offline cpu
> problem better than I originally thought. So the patch description
> is updated accordingly.
>
> This small patch series makes the cpuset hotplug a bit more efficient
> by eliminating unnecessary task iteration and cpu/node masks update
> when a cpu hotplug event (online/offline) happens.
>
> It can also largely work around the known problem of missing previously
> offlined cpus in v1 cpuset with some exceptions.
Imma hold on these patches for now. Let's see how the regression fix goes
and revisit after the merge window.
Thanks.
--
tejun
next prev parent reply other threads:[~2023-02-02 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-02 14:31 Waiman Long
2023-02-02 14:31 ` [PATCH v2 1/2] cgroup/cpuset: Skip task update if hotplug doesn't affect current cpuset Waiman Long
2023-02-02 14:32 ` [PATCH v2 2/2] cgroup/cpuset: Don't update tasks' cpumasks for cpu offline events Waiman Long
2023-02-04 9:40 ` Peter Zijlstra
2023-02-05 4:40 ` Waiman Long
2023-02-05 16:34 ` Waiman Long
2023-02-02 21:52 ` Tejun Heo [this message]
2023-02-03 12:07 ` [PATCH v2 0/2] cgroup/cpuset: Make hotplug code more efficient Will Deacon
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=Y9wwrvRDCspI6fhT@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=peterz@infradead.org \
--cc=will@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®