linux-kernel - Re: [RFC PATCH] sched/fair: Optionally restrict SMT scheduling ("restrict

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 02 Feb 2018 16:14:01 +0100
From:   Sergio Lopez <slp@...rega.org>
To:     Mike Galbraith <efault@....de>, linux-kernel@...r.kernel.org
Cc:     mingo@...hat.com, peterz@...radead.org
Subject: Re: [RFC PATCH] sched/fair: Optionally restrict SMT scheduling
 ("restrict_smt")

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.

Sergio.