On Fri, 2005-12-02 at 16:19 -0800, George Anzinger wrote:
> john stultz wrote:
> > All,
> > Here is the second of two patches which try to minimize my ntp rework
> > patches.
> >
> > This patch further changes the interrupt time NTP code, breaking out the
> > leapsecond processing and introduces an accessor to a shifted ppm
>
> In a discusson aroung the leapsecond and how to disable it (some folks
> don't want the time jump) it came to light that, for the most part,
> this is unused code. It requires that time be kept in UST to be
> useful and, from what I can tell, most folks keep time in their local
> timezone, thus, effectively, disableing the usage of the leapsecond
> correction (ntp figures this out and just says "no"). Possibly it is
> time to ask if we should keep this in the kernel at all.
Well, I'm trying explicitly to not change the kernel's current NTP
behavior. Instead I'm trying to allow the current NTP behavior to apply
to a continuous clocksource to avoid interpolation error and other
problems with irregular timer interrupts.
Although Its an interesting point, and I'm not opposed to discussing it,
its just not really relevant to the patch. So you might want to start a
new thread.
Also, I think the debate has been brought up a number of times on
comp.protocols.time.ntp, so you might want to check there first.
thanks
-john
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]