From: Mike Galbraith <efault@gmx.de>
To: Sergio Lopez <slp@sinrega.org>, linux-kernel@vger.kernel.org
Cc: mingo@redhat.com, peterz@infradead.org
Subject: Re: [RFC PATCH] sched/fair: Optionally restrict SMT scheduling ("restrict_smt")
Date: Fri, 02 Feb 2018 18:18:45 +0100 [thread overview]
Message-ID: <1517591925.8368.58.camel@gmx.de> (raw)
In-Reply-To: <1517584441.10356.21.camel@sinrega.org>
On Fri, 2018-02-02 at 16:14 +0100, Sergio Lopez wrote:
> On Thu, 2018-02-01 at 15:37 +0100, Mike Galbraith wrote:
> > On Thu, 2018-02-01 at 13:37 +0100, Sergio Lopez wrote:
> > > Compared against "isolcpus", "restrict_smt" presents the following
> > > advantages:
> > > - Doesn't require prior knowledge of the CPU topology, making it
> > > more friendly to both end users and automation tools.
> > > - Load balancing is still active for tasks pinned to multiple
> > > secondary SMT threads.
> >
> > This says that everybody and everything in the box is way smarter
> > than the admin.
>
> If that's an argument in favor of manual pinning and isolation, I have
> to disagree with you. That's an unnecessary burden put on the shoulders
> of the admin.
Give the admin job to one of those users you mentioned who knows which
threads are "secondary" threads, he/she won't be burdened at all.
-Mike
prev parent reply other threads:[~2018-02-02 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 12:37 [RFC PATCH] sched/fair: Optionally restrict SMT scheduling ("restrict_smt") Sergio Lopez
2018-02-01 14:37 ` Mike Galbraith
2018-02-02 15:14 ` Sergio Lopez
2018-02-02 17:18 ` Mike Galbraith [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=1517591925.8368.58.camel@gmx.de \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=slp@sinrega.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox