[lkml]   [2005]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: CONFIG_PRINTK_TIME woes wrote:
> At the other extreme ... the current use of sched_clock() with
> potentially nano-second resolution is way over the top. Logging
> to a serial console at 115200 a typical line from printk will take
> 2-4 milli-seconds to print ... so there would seem to be little
> benefit from a sub-millisecond resolution (in fact at 250HZ jiffies
> are on the ragged edge of being good enough).
> If that isn't sufficient ... it should be possible to make a cut-down,
> lockless version of do_gettimeofday that meets Andrew's suggestion
> of good resolution with occasional theoretical weirdness. But before
> we go there ... I'd like to hear whether there are usage models that
> really need better resolution than jiffies can provide?

I think so. Say you're debugging or performance tuning filesystem requests
and I/O completions, etc. You disable the console with `dmesg -n', run the
test then do `dmesg -s 1000000 > foo'. Having somewhat-sub-millisecond
timestamping in the resulting trace is required.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-08-22 22:17    [W:0.083 / U:0.496 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site