linux-kernel - Re: Core Scheduling

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] [day] [month] [year] [list]

Date:   Tue, 27 Jul 2021 11:54:38 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Joel Fernandes <joelaf@...gle.com>
Cc:     "Rajendran, Jaishankar" <jaishankar.rajendran@...el.com>,
        Dario Faggioli <dfaggioli@...e.com>,
        Vineeth Pillai <vineethrp@...il.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Mallikarjun Chegaraddi, Raju" 
        <raju.mallikarjun.chegaraddi@...el.com>
Subject: Re: Core Scheduling - Concurrent VMs

On Mon, Jul 26, 2021 at 11:57:21AM -0400, Joel Fernandes wrote:
> Hi,
> +Dario Faggioli and +Vineeth Pillai as well.
> 
> On Mon, Jul 26, 2021 at 1:41 AM Rajendran, Jaishankar
> <jaishankar.rajendran@...el.com> wrote:
> >
> > Refer to the below experiments performed using Core Scheduling for Concurrent VMs and we found the benchmark scores executed in different VMs are
> > degrading after enablement of Core Scheduling. Both the host and guest are enabled with Core Scheduler
> 
> Why are you running core scheduling within the guest? Only the host
> needs it and you tag vCPU threads in the host. Within the guest you
> don't need it (and it probably doesn't make sense unless you pin the
> vCPU threads to individual physical hardware threads).

Correct, in-guest core-scheduling only works if there's an in-guest
topology, which requires pinning vcpu threads and sacrificing a chicken
on the altar of qemu to get the right incantation such that the guest
actually receives the right topology.

Nested core scheduling hurts my head.

> I don't think these commands can really tell you that core scheduler
> is working or not. They are too coarse grained. You would need to look
> at it through ftrace scheduling events. Core scheduling will still
> allow differently tagged threads to use a core, it is just that it
> wont allow it simultaneously.

Right, you need tracing to verify it actually works, no real alternative
there.