linux-kernel - Re: [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2

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:	Wed, 26 Jul 2006 07:28:19 -0400
From:	Valdis.Kletnieks@...edu
To:	Al Boldi <a1426z@...ab.com>
Cc:	Peter Williams <pwil3058@...pond.net.au>,
	linux-kernel@...r.kernel.org
Subject: Re: [ANNOUNCE][RFC] PlugSched-6.4 for 2.6.18-rc2

On Wed, 26 Jul 2006 07:45:33 +0300, Al Boldi said:
> Valdis.Kletnieks@...edu wrote:

> > On an SMP system, you can have one CPU doing one class of scheduling (long
> > timeslice for computational, for example), while another CPU is dedicated
> > to doing RT scheduling, and so on.  It's not clear to me that "different
> > classes per CPU" makes any real sense on a UP....
> 
> Conceptually there should be no difference between UP and MP.
> 
> Think HyperThreading.

Which is why a UP kernel can schedule on both sides of an HT core.

Yeah, I got it now. ;)

An HT core still *has* "the other instruction stream" it can schedule
differetly.  You can't say "We'll schedule this one this way and that other
one that way" when there *is* no "that other one".

(And if you look at the current code, you'll realize that HT is conceptually
different from both UP *and* MP - go look at the places where the *current*
scheduler is HT-aware, and how that was a big win over when it thought each
HT was a fully capable MP......)

Content of type "application/pgp-signature" skipped