Re: CONFIG_PRINTK_TIME woes

>How fast is printk?  I haven't looked.
>
>ie: if you do back-to-back printk's, what's the timestamp increment?

On ia64 it looks like about 4-5 usec increment for back-to-back
printk (with no serial console configured, and dmesg -n to turn
off messages to the VGA console).

-Tony
-
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: Andrew Morton <[email protected]>

• References:
  • RE: CONFIG_PRINTK_TIME woes
    • From: [email protected]
  • Re: CONFIG_PRINTK_TIME woes
    • From: "David S. Miller" <[email protected]>
  • Re: CONFIG_PRINTK_TIME woes
    • From: Jason Uhlenkott <[email protected]>
  • Re: CONFIG_PRINTK_TIME woes
    • From: "David S. Miller" <[email protected]>
  • Re: CONFIG_PRINTK_TIME woes
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: [patch 8/8] [PATCH] Module per-cpu alignment cannot always be met
• Next by Date: Re: [PATCH] ia64 cpuset + build_sched_domains() mangles structures
• 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]