Linux cgroups development
 help / color / mirror / Atom feed
From: Guopeng Zhang <zhangguopeng@kylinos.cn>
To: longman@redhat.com, tj@kernel.org, juri.lelli@redhat.com,
	chenridong@huaweicloud.com, mkoutny@suse.com
Cc: hannes@cmpxchg.org, mingo@redhat.com, peterz@infradead.org,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, kprateek.nayak@amd.com,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: make DL attach bandwidth reservation root-domain aware
Date: Wed, 22 Apr 2026 10:14:08 +0800	[thread overview]
Message-ID: <bca5f779-1550-45af-a0d0-74b427b25c8f@kylinos.cn> (raw)
In-Reply-To: <20260421083449.95750-1-zhangguopeng@kylinos.cn>

Hi,

For another case Waiman raised while reviewing the "record DL BW
alloc CPU for attach rollback" patch, I did some validation and
summarized the test results here:

https://lore.kernel.org/all/d683b3c8-f746-47cd-a306-314a8f3eecea@kylinos.cn/

In short, the data there shows that the same-root-domain case can
indeed leave persistent extra DL bandwidth accounting before the fix,
while the follow-up patch removes that growth and still preserves the
expected cross-root-domain bandwidth transfer behavior.

Thanks,
Guopeng
在 2026/4/21 16:34, Guopeng Zhang 写道:
> [PATCH] cgroup/cpuset: make DL attach bandwidth reservation root-domain aware

  reply	other threads:[~2026-04-22  2:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  8:34 [PATCH] cgroup/cpuset: make DL attach bandwidth reservation root-domain aware Guopeng Zhang
2026-04-22  2:14 ` Guopeng Zhang [this message]
2026-04-24 14:15 ` Waiman Long
2026-04-26 13:48   ` Guopeng Zhang
2026-04-27 13:47     ` Waiman Long
2026-04-30  8:53   ` Guopeng Zhang
2026-04-30 12:39     ` 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=bca5f779-1550-45af-a0d0-74b427b25c8f@kylinos.cn \
    --to=zhangguopeng@kylinos.cn \
    --cc=bsegall@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=chenridong@huaweicloud.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=juri.lelli@redhat.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=mkoutny@suse.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tj@kernel.org \
    --cc=vincent.guittot@linaro.org \
    --cc=vschneid@redhat.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