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]
Message-ID: <4FCCD0CD.8080700@linux.intel.com>
Date:	Mon, 04 Jun 2012 08:14:21 -0700
From:	Arjan van de Ven <arjan@...ux.intel.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
CC:	Vladimir Davydov <vdavydov@...allels.com>,
	Ingo Molnar <mingo@...e.hu>, Len Brown <lenb@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] cpuidle: menu: use nr_running instead of cpuload for
 calculating perf mult

On 6/4/2012 8:08 AM, Peter Zijlstra wrote:
> On Mon, 2012-06-04 at 06:48 -0700, Arjan van de Ven wrote:
>> it's not about busy, it's about performance sensitive.
>> it's not a super nice proxy, no argument, but it's one of the few long
>> term ones we have.
>>
> I'm still not seeing how it makes any sense at all. Is there an actual
> workload here this matters?

yes there are, mostly server ones.

the problem isn't an individual idle, it's that the 100us-200us
latencies add up if you go in and out repeatedly, when the system is in
a situation where it is sensitive to performance (which is not an
instant thing, this is a "over the long run we're busy" thing)...
... they become a real factor.

now, "performance sensitive" is highly elusive and unmeasureable, but
load average is a reasonable approximation... well, the best we have.
(just cpu usage is not, you can have low cpu usage but block on
semaphores or IO all the time, and you're still sensitive to performance)
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ