From: Jason Uhlenkott <jasonuhl@sgi.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: tony.luck@intel.com, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: CONFIG_PRINTK_TIME woes
Date: Mon, 22 Aug 2005 13:33:06 -0700 [thread overview]
Message-ID: <20050822203306.GA897956@dragonfly.engr.sgi.com> (raw)
In-Reply-To: <20050822.132052.65406121.davem@davemloft.net>
On Mon, Aug 22, 2005 at 01:20:52PM -0700, David S. Miller wrote:
> From: tony.luck@intel.com
> 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.
next prev parent reply other threads:[~2005-08-22 20:33 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 [this message]
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
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=20050822203306.GA897956@dragonfly.engr.sgi.com \
--to=jasonuhl@sgi.com \
--cc=akpm@osdl.org \
--cc=davem@davemloft.net \
--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
Powered by JetHome