From: Frederic Weisbecker <frederic@kernel.org>
To: Yu Liao <liaoyu15@huawei.com>
Cc: paulmck@kernel.org, linux-kernel@vger.kernel.org,
liwei391@huawei.com, rcu@vger.kernel.org
Subject: Re: Question about nohz and sysidle
Date: Mon, 14 Feb 2022 11:57:44 +0100 [thread overview]
Message-ID: <20220214105744.GA663287@lothringen> (raw)
In-Reply-To: <b6dc758b-492d-1000-24e5-643e38d3166e@huawei.com>
On Mon, Feb 14, 2022 at 05:40:55PM +0800, Yu Liao wrote:
Hi Yu Liao,
>
> On 2022/2/14 16:28, Yu Liao wrote:
> > Hi Frederic,
> >
> > I'm working on an issue about nohz. When NO_HZ_FULL is enabled, CPU 0
> > handles the timekeeping duty on behalf of all other CPUs, which means
> > CPU 0 never stop tick even in sysidle state. This is a powersaving
> > issue.
> >
> > I found your patchset (nohz: Support sysidle) in the below link.
> > https://lore.kernel.org/all/1406569056-30217-1-git-send-email-fweisbec@gmail.com/
> >
> > But these patches haven't been merged into mainline yet and sysidle
> > state detection has been removed by commit fe5ac724d81a (rcu: Remove
> > nohz_full full-system-idle state machine) as well.
> >
> > I tried your patches and it does work, why are we no longer working on
> > stopping timekeeping duty when all full dynticks CPUs are idle?
Because it was not a priority at that time. There were so many things to handle
first (and we are not even done yet) that we postponed that feature until
someone ever comes up with powersaving issues on nohz_full. We were waiting for
you :)
It's possible to unearth this. I think the first step will be to merge the
RCU dynticks counters into context tracking, something that was on my queue
anyway, and then revive this:
https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git/commit/?h=sysidle.2017.05.11a&id=fe5ac724d81a3c7803e60c2232718f212f3f38d4
Thanks.
next prev parent reply other threads:[~2022-02-14 11:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 8:28 Yu Liao
2022-02-14 9:40 ` Yu Liao
2022-02-14 10:57 ` Frederic Weisbecker [this message]
2022-02-14 14:49 ` Paul E. McKenney
2022-02-15 1:57 ` Xiongfeng Wang
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=20220214105744.GA663287@lothringen \
--to=frederic@kernel.org \
--cc=liaoyu15@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liwei391@huawei.com \
--cc=paulmck@kernel.org \
--cc=rcu@vger.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®