[lkml]   [2019]   [Apr]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/4] Allow CPU0 to be nohz full
Thomas Gleixner's on April 5, 2019 12:36 am:
> On Thu, 4 Apr 2019, Nicholas Piggin wrote:
>> I've been looking at ways to fix suspend breakage with CPU0 as a
>> nohz CPU. I started looking at various things like allowing CPU0
>> to take over do_timer again temporarily or allowing nohz full
>> to be stopped at runtime (that is quite a significant change for
>> little real benefit). The problem then was having the housekeeping
>> CPU go offline.
>> So I decided to try just allowing the freeze to occur on non-zero
>> CPU. This seems to be a lot simpler to get working, but I guess
>> some archs won't be able to deal with this? Would it be okay to
>> make it opt-in per arch?
> It needs to be opt in. x86 will fall on its nose with that.

Okay I can add that.

> Now the real interesting question is WHY do we need that at all?

Why full nohz for CPU0? Basically this is how their job system was
written and used, testing nohz full was a change that came much later
as an optimisation.

I don't think there is a fundamental reason an equivalent system
could not be made that uses a different CPU for housekeeping, but I
was assured the change would be quite difficult for them.

If we can support it, it seems nice if you can take a particular
configuration and just apply nohz_full to your application processors
without any other changes.


 \ /
  Last update: 2019-04-04 18:03    [W:0.070 / U:5.108 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site