From: Frederic Weisbecker <frederic@kernel.org>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Phil Auld <pauld@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E. McKenney" <paulmck@kernel.org>,
Joel Fernandes <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org
Subject: Re: Requirements to control kernel isolation/nohz_full at runtime
Date: Thu, 10 Sep 2020 00:38:56 +0200 [thread overview]
Message-ID: <20200909223856.GB20541@lenoir> (raw)
In-Reply-To: <20200903185200.GA1029791@fuller.cnet>
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?
next prev parent reply other threads:[~2020-09-09 22:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 10:46 Requirements to control kernel isolation/nohz_full at runtime Frederic Weisbecker
2020-09-03 18:23 ` Marcelo Tosatti
2020-09-03 18:30 ` Marcelo Tosatti
2020-09-03 18:36 ` Phil Auld
2020-09-03 18:52 ` Marcelo Tosatti
2020-09-09 22:38 ` Frederic Weisbecker [this message]
2020-09-09 22:34 ` Frederic Weisbecker
2020-09-04 20:47 ` Paul E. McKenney
2020-09-09 22:48 ` Frederic Weisbecker
2020-09-07 15:34 ` peterz
2020-09-09 23:02 ` Frederic Weisbecker
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=20200909223856.GB20541@lenoir \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pauld@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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.