linux-kernel - Re: Stolen and degraded time and schedulers

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, 14 Mar 2007 11:12:17 -0400
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Dan Hecht <dhecht@...are.com>, dwalker@...sta.com,
	cpufreq@...ts.linux.org.uk,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Con Kolivas <kernel@...ivas.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Virtualization Mailing List <virtualization@...ts.osdl.org>,
	john stultz <johnstul@...ibm.com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: Stolen and degraded time and schedulers

On Wed, Mar 14, 2007 at 08:08:17AM -0700, Jeremy Fitzhardinge wrote:
> You're right.  That's a very tough case.  I don't know if there's any
> way to do a reasonable estimate of the slowdown.  You could handwave it
> and say "if both threads are running a process, then apply an X scaling
> factor to their rate of progress".  That might be enough.

I would think that's a bad idea.  I expect future processors to do HT
much better than the P4 did.  There will always be cases where two
processes don't share well, but the majority of cases they probably will
share well.  Of course if you don't have enough processes to keep all
the CPU cores busy, you might as well not schedule something on the
siblings on HT processors, but on the other hand maybe you should if you
can power down other cpus completely to save power and still get all the
work done at maximum speed.

--
Len Sorensen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/