linux-kernel - Re: [PATCH] timers: more consistently use clock vs timer

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] [day] [month] [year] [list]

Message-ID: <20090213120430.GA5483@elte.hu>
Date:	Fri, 13 Feb 2009 13:04:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	L-K <linux-kernel@...r.kernel.org>,
	Oleg Nesterov <oleg@...hat.com>
Subject: Re: [PATCH] timers: more consistently use clock vs timer


* Peter Zijlstra <peterz@...radead.org> wrote:

> Subject: timers: more consistently use clock vs timer
> From: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> Date: Thu Feb 12 15:00:52 CET 2009
> 
> While reviewing the manpages, I noticed I'd missed some clock vs timer sites.
> 
> Make sure that all timer functions call cpu_timer_sample_group() and not
> cpu_clock_sample_group(). This ensures that we enable the process wide timer
> in time, and therefore pay the O(n) thread group cost from the syscall.
> 
> Not doing it here, will result in the first jiffy tick after setting the timer
> doing this, resulting in a very expensive tick (but only once) and a delay in
> actually starting the timer.
> 
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> ---
>  kernel/posix-cpu-timers.c |   60 +++++++++++++++++++++++-----------------------
>  1 file changed, 30 insertions(+), 30 deletions(-)

Applied to tip:timers/urgent, thanks Peter!

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