On Tue, 2005-08-23 at 17:29 -0700, George Anzinger wrote:
> Roman Zippel wrote:
> > Hi,
> >
> > On Tue, 23 Aug 2005, john stultz wrote:
> >
> >
> >>I'm assuming gettimeofday()/clock_gettime() looks something like:
> >> xtime + (get_cycles()-last_update)*(mult+ntp_adj)>>shift
> >
> >
> > Where did you get the ntp_adj from? It's not in my example.
> > gettimeofday() was in the previous mail: "xtime + (cycle_offset * mult +
> > error) >> shift". The difference between system time and reference
> > time is really important. gettimeofday() returns the system time, NTP
> > controls the reference time and these two are synchronized regularly.
> > I didn't see that anywhere in your example.
> >
> If I read your example right, the problem is when the NTP adjustment
> changes while the two clocks are out of sync (because of a late tick).
Not quite. The issue that I'm trying to describe is that if, we
inconsistently calculate time intervals in gettimeofday and the timer
interrupt, we have the possibility for time inconsistencies.
The trivial example using the current code would be something like:
Again with my 2 cyc per tick clock, HZ=1000.
gettimeofday():
xtime + offset_ns
timer_interrupt:
xtime += tick_length + ntp_adj
offset_ns = 0
0: gettimeofday: 0 + 0 = 0 ns
1: gettimeofday: 0 + 500k ns = 500k ns
2: gettimeofday: 0 + 1M ns = 1M ns
2: timer_interrupt:
2: gettimeofday: 1M ns + 0 ns = 1M ns
3: gettimeofday: 1M ns + 500k ns = 1.5M ns
4: gettimeofday: 1M ns + 1M ns = 2 ns
4: timer_interrupt (using -500ppm adjustment)
4: gettimeofday: 1,999,500 ns + 0 ns = 1,999,500 ns
> It would appear that gettimeofday would need to know that the NTP
> adjustment is changing (and to what). It would also appear that this
> is known by the ntp code and could be made available to gettimeofday.
> If it is changing due to an NTP call, that system call, itself,
> should/must force synchronization. So the only case gettimeofday needs
> to worry/know about is that an adjustment is to change at time X to
> value Y. Also, me thinks there is only one such change that can be
> present at any given time.
Well, in many arches gettimeofday() works around the above issue by
capping the offset_ns value as such:
gettimeofday:
xtime + min(offset_ns, tick_len + ntp_adj)
The problem with this is that when we have lost or late ticks, or if we
are using dynamic ticks you have granularity problems.
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |