linux-kernel - Re: scheduler vs hardware? (was Re: another i7 (linux) bug?)

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, 22 Jan 2010 09:58:42 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Luca Zini <luca.zini@...il.com>
CC:	Mike Galbraith <efault@....de>,
	Peter Zijlstra <peterz@...radead.org>, aagaande@...il.com,
	rdelcueto@...mail.com, mingo@...e.hu,
	linux-kernel <linux-kernel@...r.kernel.org>,
	Alex Chiang <achiang@...com>
Subject: Re: scheduler vs hardware? (was Re: another i7  (linux) bug?)


On 01/22/2010 05:22 AM, Luca Zini wrote:

> with nice set to 19 a processor 3 reach the maximum speed,  with nice
set to
> -20 its maximum value is 300-400 mhz under the maximum value.

I wonder if at lower nice levels the timing on something changes,
forcing multiple cores to be active just often enough to keep the i7
from doing the turbo boost thing, whereas with higher nice levels
everything is serialized allowing the boost to be enabled.

Chris
--
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/