Re: CONFIG_PRINTK_TIME woes

From: [email protected]
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.
-
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/

---

• Follow-Ups:
  • Re: CONFIG_PRINTK_TIME woes
    • From: Jason Uhlenkott <[email protected]>

• References:
  • Re: CONFIG_PRINTK_TIME woes
    • From: Andrew Morton <[email protected]>
  • Re: CONFIG_PRINTK_TIME woes
    • From: Andrew Morton <[email protected]>
  • RE: CONFIG_PRINTK_TIME woes
    • From: [email protected]

• Prev by Date: Re: [RFC] [patch 0/39] remap_file_pages protection support, try 2
• Next by Date: Re: skge missing ifdefs.
• Previous by thread: Re: CONFIG_PRINTK_TIME woes
• Next by thread: Re: CONFIG_PRINTK_TIME woes
• Index(es):
  • Date
  • Thread

[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]