[lkml]   [2010]   [May]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] x86: Export tsc related information in sysfs
On 05/24/2010 04:16 PM, Dan Magenheimer wrote:
>> From: john stultz []
>> Also, you don't really need extra accuracy, you just need it to be the
>> same from boot to boot. NTP keeps the correction factor persistent from
>> boot to boot via the drift file. The boot argument is just trying to
>> save the time (possibly hours depending on ntp config) after a reboot
>> for NTP to correct for the new error introduced by calibration.
> I was assuming that extra accuracy would decrease the ntp
> convergence time by about the same factor (5-6 bits of extra
> accuracy would decrease ntp convergence time by 32-64x).
> Is that an incorrect assumption?


>> From: H. Peter Anvin []
>> A longer sample would make sense if the goal is to freeze it into a
>> kernel command line variable, but the real question is how many people
>> would actually do that (and how many people would then suffer problems
>> because they upgraded their CPU/mobo and got massive failures on post-
>> boot.)
> Not sure why upgraded mobo's would fail due to a longer sample?

Not due to a longer sample, but a frozen sample.

> As more and more systems become dependent on clocksource==tsc
> and more and more people assume nanosecond-class measurements
> are relatively accurate, I'd expect the accuracy of tsc_khz
> to become more important. While desktop users might bristle
> at an extra second of boot delay, I'll bet many server
> farm administrators would gladly pay that upfront cost
> if they know an option exists.

Not really. The delta measurements aren't the issue here, but rather
walltime convergence.


 \ /
  Last update: 2010-05-25 01:25    [W:0.071 / U:5.776 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site