From: Frederic Weisbecker <frederic@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Yun Levi <ppbuk5246@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Vineeth Pillai <vineeth@bitbyteword.org>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
anna-maria@linutronix.de, mingo@kernel.org, tglx@linutronix.de,
Markus.Elfring@web.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] time/tick-sched: idle load balancing when nohz_full cpu becomes idle.
Date: Fri, 17 May 2024 16:50:56 +0200 [thread overview]
Message-ID: <Zkdu0Guz8ySN2Qoe@localhost.localdomain> (raw)
In-Reply-To: <20240516175321.GN22557@noisy.programming.kicks-ass.net>
Le Thu, May 16, 2024 at 07:53:21PM +0200, Peter Zijlstra a écrit :
> On Thu, May 16, 2024 at 05:32:56PM +0200, Frederic Weisbecker wrote:
> > On Thu, May 16, 2024 at 05:19:53PM +0200, Peter Zijlstra wrote:
>
> > > Yes, but stronger, as long as the CPU is part of a load-balance domain,
> > > it must not disable the tick while running anything.
> > >
> > > that is, NOHZ_FULL must not become active unless it's running on a
> > > single CPU partition.
> >
> > I like the idea but I'm afraid to introduce regressions while doing so,
> > with people currently using nohz_full without proper partionning...
>
> There is no regression, if this is possible today it is utterly broken.
>
> This should never have been possible.
Ok, I'll try something.
Thanks.
prev parent reply other threads:[~2024-05-17 14:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 21:31 [PATCH] time/tick-sched: enable idle load balancing when nohz_full cpu becomes idle Levi Yun
2024-05-08 9:18 ` Markus Elfring
2024-05-09 9:59 ` Dan Carpenter
2024-05-08 17:26 ` [PATCH v2] time/tick-sched: " Levi Yun
2024-05-08 18:38 ` Markus Elfring
2024-05-08 19:15 ` Yun Levi
2024-05-08 19:22 ` [PATCH v3] " Levi Yun
2024-05-09 6:28 ` Markus Elfring
2024-05-09 7:26 ` Yun Levi
2024-05-09 8:16 ` Markus Elfring
2024-05-09 9:22 ` Yun Levi
2024-05-09 9:40 ` [v3] " Markus Elfring
2024-05-09 9:29 ` [PATCH v4] " Levi Yun
2024-05-09 9:55 ` [v4] " Markus Elfring
2024-05-15 16:41 ` [PATCH v4] " Yun Levi
2024-05-15 22:52 ` Frederic Weisbecker
2024-05-16 5:29 ` Yun Levi
2024-05-16 7:56 ` Peter Zijlstra
2024-05-16 8:20 ` Yun Levi
2024-05-16 8:49 ` Peter Zijlstra
2024-05-16 11:25 ` Frederic Weisbecker
2024-05-16 12:43 ` Yun Levi
2024-05-16 14:00 ` Peter Zijlstra
2024-05-16 14:23 ` Frederic Weisbecker
2024-05-16 14:45 ` Peter Zijlstra
2024-05-16 15:02 ` Frederic Weisbecker
2024-05-16 15:19 ` Peter Zijlstra
2024-05-16 15:32 ` Frederic Weisbecker
2024-05-16 16:12 ` Yun Levi
2024-05-16 17:53 ` Peter Zijlstra
2024-05-17 14:50 ` Frederic Weisbecker [this message]
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=Zkdu0Guz8ySN2Qoe@localhost.localdomain \
--to=frederic@kernel.org \
--cc=Markus.Elfring@web.de \
--cc=anna-maria@linutronix.de \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=ppbuk5246@gmail.com \
--cc=tglx@linutronix.de \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.