lkml.org 
[lkml]   [2020]   [Sep]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Requirements to control kernel isolation/nohz_full at runtime
On Thu, Sep 03, 2020 at 03:52:00PM -0300, Marcelo Tosatti wrote:
> On Thu, Sep 03, 2020 at 02:36:36PM -0400, Phil Auld wrote:
> > exclusive cpusets is used now to control scheduler load balancing on
> > a group of cpus. It seems to me that this is the same idea and is part
> > of the isolation concept. Having a toggle for each subsystem/feature in
> > cpusets could provide the needed userspace api.
> >
> > Under the covers it might be implemented as twiddling various cpumasks.
> >
> > We need to be shifting to managing load balancing with cpusets anyway.
>
> OK, adding a new file per isolation feature:
>
> - cpuset.isolation_nohz_full
> - cpuset.isolation_kthread
> - cpuset.isolation_time
>
> With a bool value per file, is an option.

Exactly. I would merge kthread/timers/workqueue into
cpuset.isolation.unbound though. Unless anyone may need more
granularity there?

\
 
 \ /
  Last update: 2020-09-10 00:39    [W:0.123 / U:0.592 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site