From: Joe Korty <joe.korty@ccur.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "mingo@elte.hu" <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] shrink printk timestamp field
Date: Sat, 30 Aug 2008 10:38:08 -0400 [thread overview]
Message-ID: <20080830143808.GA10821@tsunami.ccur.com> (raw)
In-Reply-To: <20080829163540.634e86d9.akpm@linux-foundation.org>
On Fri, Aug 29, 2008 at 07:35:40PM -0400, Andrew Morton wrote:
> On Wed, 27 Aug 2008 11:17:59 -0400 Joe Korty <joe.korty@ccur.com> wrote:
>
> > Shrink the printk timestamp field.
> >
> > Keep the printk timestamp from occupying more of the
> > scarce, 80-column console line space than it really needs.
> >
>
> This is a significant loss in utility.
>
> [ 16.817285] md: Autodetecting RAID arrays.
> [ 16.817288] md: Scanned 0 and added 0 devices.
> [ 16.817290] md: autorun ...
> [ 16.817292] md: ... autorun DONE.
>
> This not-terribly-fast machine can emit printks into the log buffer
> within two microseconds. That's a pretty useful ad-hoc timing
> factility.
>
> This patch will reduce the precision by a factor of five hundred.
I was looking at it from the point of view of finding out where the
boot process was too slow. For that millisecs is enough. I am not
sure where knowing printk output to the microsec would be useful for
solving anything.
Joe
next prev parent reply other threads:[~2008-08-30 14:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 15:17 [PATCH] shrink printk timestamp field Joe Korty
2008-08-28 9:38 ` Ingo Molnar
2008-08-29 23:35 ` Andrew Morton
2008-08-30 14:38 ` Joe Korty [this message]
2008-08-30 17:16 ` Andrew Morton
2008-08-30 17:47 ` Leon Woestenberg
2008-08-30 18:57 ` Joe Korty
2008-09-06 18:24 ` Ingo Molnar
2008-09-01 8:31 ` Benny Halevy
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=20080830143808.GA10821@tsunami.ccur.com \
--to=joe.korty@ccur.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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