cgroups.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Xin Zhao <jackzxcui1989@163.com>
Cc: tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
	mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
	vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
	rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
	vschneid@redhat.com, will@kernel.org, boqun.feng@gmail.com,
	longman@redhat.com, clrkwllms@kernel.org,
	cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH] sched/cgroup: Lock optimize for cgroup cpu throttle
Date: Tue, 19 Aug 2025 15:06:56 +0200	[thread overview]
Message-ID: <20250819130656.DdJqAScZ@linutronix.de> (raw)
In-Reply-To: <20250811151316.838707-1-jackzxcui1989@163.com>

On 2025-08-11 23:13:16 [+0800], Xin Zhao wrote:
> Dear Sebastian,
> 
> I believe what you mentioned is related to the same issue that Valentin
> brought up later, which is the current solution of "delaying CPU throttling
> through the task_work mechanism until returning to user mode."
> My colleagues and I indeed noticed this from the beginning. However, on our
> 6.1.134 RT-Linux system, we have tried new versions of this solution one by
> one, but they have all failed during basic script tests, so none have reached
> the stage of being used in our project. I see that this modification has been
> promoted in the community for more than two years, yet it remains in a state
> that doesn't work well (on our 6.1.134 RT-Linux system). I wonder if the
> changes require too many considerations or if this modification simply isn't
> suitable for running on RT-Linux. Our project cannot afford to wait, and
> there are many performance issues in RT-Linux.

You are free to use the patch.
Based on your description I assume that the patch Valentin referenced
will solve your problem. If not, it will be interesting to know why it
is not working. Otherwise you keep maintaining your patch.

> Thanks
> Xin Zhao

Sebastian

  reply	other threads:[~2025-08-19 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 15:13 [PATCH] sched/cgroup: Lock optimize for cgroup cpu throttle Xin Zhao
2025-08-19 13:06 ` Sebastian Andrzej Siewior [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-20  8:04 Xin Zhao
2025-08-11 16:04 Xin Zhao
2025-08-19 11:28 ` Valentin Schneider
2025-08-11  7:08 Xin Zhao
2025-08-11  8:36 ` Sebastian Andrzej Siewior
2025-08-11 14:18   ` Valentin Schneider

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=20250819130656.DdJqAScZ@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=boqun.feng@gmail.com \
    --cc=bsegall@google.com \
    --cc=cgroups@vger.kernel.org \
    --cc=clrkwllms@kernel.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=hannes@cmpxchg.org \
    --cc=jackzxcui1989@163.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --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 \
    --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;
as well as URLs for NNTP newsgroup(s).