linux-kernel - Re: [patch] dynticks core: Fix idle time accounting

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, 04 Oct 2006 05:58:07 -0400
From:	Valdis.Kletnieks@...edu
To:	Ingo Molnar <mingo@...e.hu>
Cc:	tglx@...utronix.de, Andrew Morton <akpm@...l.org>,
	LKML <linux-kernel@...r.kernel.org>, Jim Gettys <jg@...top.org>,
	John Stultz <johnstul@...ibm.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [patch] dynticks core: Fix idle time accounting

On Wed, 04 Oct 2006 09:56:57 +0200, Ingo Molnar said:
> 
> * Valdis.Kletnieks@...edu <Valdis.Kletnieks@...edu> wrote:
> 
> > Even though I have CONFIG_HZ=1000, this ends up generating a synthetic 
> > count that works out to 100 per second.  gkrellm and vmstat are happy 
> > with that state of affairs, but I'm not sure why it came out to 
> > 100/sec rather than 1000/sec.
> 
> that's how it worked for quite some time: all userspace APIs are 
> HZ-independent and depend on USER_HZ (which is 100 even if HZ is 1000).

Nevermind - I missed where fs/proc/proc_misc.c applied jiffies_64_to_clock_t()
to the number before handing it to userspace.  So the numbers *were* being
kept in terms of HZ (as my reading of the code indicated), they just didn't
manage to escape to userspace that way....




Content of type "application/pgp-signature" skipped