linux-kernel - Re: [PATCH] posix-cpu-timers: clock_gettime(CLOCK_*_CPUTIME

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: <1231401681.11687.389.camel@twins>
Date:	Thu, 08 Jan 2009 09:01:21 +0100
From:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] posix-cpu-timers: clock_gettime(CLOCK_*_CPUTIME_ID)
 goes backward

On Wed, 2009-01-07 at 18:59 +0100, Ingo Molnar wrote:
> * Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> 
> > Which reminds me, why do we still have this crap in the kernel? I 
> > thought we pretty much showed the per-cpu itimer thing was utter crap? 
> > -- can we pretty please either revert that or apply 
> > http://lkml.org/lkml/2008/11/24/183 ?
> > 
> > Also, I really don't like the above, we now do the per-cpu loop with the 
> > RQ lock held...
> 
> ok, i've applied it to tip/timers/urgent. This should solve the original 
> itimer testcase as well, correct?

Yeah, but what would need to happen to make itimers not lock up large
machines is reduce its granularity depeding on machine size.

The whole (process wide) itimer idea just plain sucks -- sadly its part
of unix so we can't just drop it, the best we can do is make it useless
(but within spec) so that nobody sane will use it ;-)

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