[lkml]   [2005]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: CONFIG_PRINTK_TIME woes
    On Mon, Aug 22, 2005 at 01:20:52PM -0700, David S. Miller wrote:
    > From:
    > Date: Mon, 22 Aug 2005 10:42:22 -0700
    > > At the other extreme ... the current use of sched_clock() with
    > > potentially nano-second resolution is way over the top.
    > Not really, when I'm debugging TCP events over gigabit
    > these timestamps are exceptionally handy.

    Yes, but how many of those figures are really significant? I strongly
    suspect that the overhead of printk() is high enough, even when we're
    just spewing to the dmesg buffer and not the console, that we have a
    lot more precision than accuracy at nanosecond resolution.
    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:35    [W:0.022 / U:0.144 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site