[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 1 Jan 2007 17:27:45 +0100
From: Roman Zippel <zippel@...ux-m68k.org>
To: john stultz <johnstul@...ibm.com>
Cc: Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] HZ free ntp
Hi,
On Wednesday 20 December 2006 02:32, john stultz wrote:
> > I know and all you have to change in the ntp and some related code is to
> > replace HZ there with a variable, thus make it changable, so you can
> > increase the update interval (i.e. it becomes 1s/hz instead of 1s/HZ).
>
> Untested patch below. Does this vibe better with you are suggesting?
Yes, thanks.
tick_nsec doesn't require special treatment, in the middle term it's obsolete
anyway, it could be replaced with (current_tick_length() >>
TICK_LENGTH_SHIFT) and current_tick_length() being inlined.
NTP_INTERVAL_FREQ could be a real variable (so it can be initialized at
runtime), it's already gone from all important paths.
In the short term I'd prefered a clock would store its frequency instead of
using NTP_INTERVAL_LENGTH in clocksource_calculate_interval(), so it doesn't
has to be derived there.
bye, Roman
-
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