[lkml]   [2017]   [Aug]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH 01/12] housekeeping: Move housekeeping related code to its own file
On Thu, Aug 31, 2017 at 04:16:16PM -0400, Rik van Riel wrote:
> On Wed, 2017-08-23 at 03:51 +0200, Frederic Weisbecker wrote:
> > The housekeeping code is currently tied to the nohz code. As we are
> > planning to make housekeeping independant from it, start with moving
> > the relevant code to its own file.
> >
> Why are nohz full and housekeeping being
> decoupled from each other?
> Won't people want to use them together?
> What use case am I missing?

So nohz is really just a feature and it shouldn't decide about other isolation
features. It should be the opposite: isolation picks up nohz, alongside other
isolation things. I think we did a layering misdesign. So it's mostly just a code

While at it, isolcpus= is also part of the isolation toolset. So I thought we should
centralize all this isolation code in a common subsystem.

 \ /
  Last update: 2017-09-01 00:59    [W:0.075 / U:22.508 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site