From: Qiliang Yuan <realwujing@gmail.com>
To: tj@kernel.org
Cc: longman@redhat.com, cgroups@vger.kernel.org,
akpm@linux-foundation.org, anna-maria@linutronix.de,
boqun.feng@gmail.com, bsegall@google.com,
dietmar.eggemann@arm.com, frederic@kernel.org,
hannes@cmpxchg.org, jackmanb@google.com, jiangshanlai@gmail.com,
joelagnelf@nvidia.com, josh@joshtriplett.org,
juri.lelli@redhat.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-mm@kvack.org,
mathieu.desnoyers@efficios.com, mgorman@suse.de, mhocko@suse.com,
mingo@kernel.org, mingo@redhat.com, neeraj.upadhyay@kernel.org,
paulmck@kernel.org, peterz@infradead.org, qiang.zhang@linux.dev,
rcu@vger.kernel.org, realwujing@gmail.com, rostedt@goodmis.org,
shuah@kernel.org, surenb@google.com, tglx@kernel.org,
urezki@gmail.com, vbabka@suse.cz, vincent.guittot@linaro.org,
vschneid@redhat.com, ziy@nvidia.com
Subject: Re: [PATCH 00/15] Implementation of Dynamic Housekeeping & Enhanced Isolation (DHEI)
Date: Mon, 30 Mar 2026 19:41:21 +0800 [thread overview]
Message-ID: <20260330114121.101232-1-realwujing@gmail.com> (raw)
In-Reply-To: <acQHKwGhYrpoOH1P@slm.duckdns.org>
Hi Tejun,
On Wed, Mar 25, 2026 at 04:02:44PM +0100, Tejun Heo wrote:
> This needs to be coordinated with the existing cpuset and isolation
> infrastructures.
Thank you for pointing this out. I agree that coordination is key to avoid
fragmentation of the isolation logic in the kernel.
In V13, I will focus on integrating this "Dynamic Housekeeping" logic
directly with the cpuset subsystem. The idea is to allow the root cpuset
to act as the orchestrator for both task isolation (which it already handles)
and kernel overhead isolation (which DHEI enables).
> Also, Waiman Long should definitely be in the CC list for this.
Acknowledge. I will make sure to CC Waiman and the cgroups mailing list
in the next iteration.
parent reply other threads:[~2026-03-30 11:41 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <acQHKwGhYrpoOH1P@slm.duckdns.org>]
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=20260330114121.101232-1-realwujing@gmail.com \
--to=realwujing@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=anna-maria@linutronix.de \
--cc=boqun.feng@gmail.com \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=dietmar.eggemann@arm.com \
--cc=frederic@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=jackmanb@google.com \
--cc=jiangshanlai@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=josh@joshtriplett.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qiang.zhang@linux.dev \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=tglx@kernel.org \
--cc=tj@kernel.org \
--cc=urezki@gmail.com \
--cc=vbabka@suse.cz \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=ziy@nvidia.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: 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