From: Andrew Morton <akpm@osdl.org>
To: tony.luck@intel.com
Cc: davem@davemloft.net, jasonuhl@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PRINTK_TIME woes
Date: Mon, 22 Aug 2005 15:38:38 -0700 [thread overview]
Message-ID: <20050822153838.186ac336.akpm@osdl.org> (raw)
In-Reply-To: <200508222233.j7MMXGWj020872@agluck-lia64.sc.intel.com>
tony.luck@intel.com wrote:
>
> >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).
>
Ah, thanks. Presumably it'll be considerably longer with %d's and %s's in
there. But still, ~10 usecs is good resolution for I/O operations.
next prev parent reply other threads:[~2005-08-22 22:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 18:47 Luck, Tony
2005-08-21 9:13 ` Andrew Morton
2005-08-21 9:16 ` Andrew Morton
2005-08-21 9:27 ` Nick Piggin
2005-08-21 9:32 ` Andrew Morton
2005-08-21 11:25 ` Nick Piggin
2005-08-21 18:01 ` Andrew Morton
2005-08-24 0:04 ` Tim Bird
2005-08-22 17:42 ` tony.luck
2005-08-22 17:50 ` Andrew Morton
2005-08-22 20:52 ` tony.luck
2005-08-22 20:20 ` David S. Miller
2005-08-22 20:33 ` Jason Uhlenkott
2005-08-22 20:42 ` David S. Miller
2005-08-22 21:10 ` tony.luck
2005-08-22 21:15 ` Andrew Morton
2005-08-22 22:33 ` tony.luck
2005-08-22 22:38 ` Andrew Morton [this message]
2005-08-22 23:27 ` tony.luck
2005-08-23 1:52 ` Paul Mackerras
2005-08-23 15:01 ` Nick Piggin
2005-08-24 0:36 ` Tim Bird
2005-08-23 7:18 ` Tony Lindgren
2005-08-23 14:07 Luck, Tony
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050822153838.186ac336.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=jasonuhl@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®