Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755915AbYH3S54 (ORCPT ); Sat, 30 Aug 2008 14:57:56 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753691AbYH3S5t (ORCPT ); Sat, 30 Aug 2008 14:57:49 -0400 Received: from flusers.ccur.com ([12.192.68.2]:57271 "EHLO gamx.iccur.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753569AbYH3S5s (ORCPT ); Sat, 30 Aug 2008 14:57:48 -0400 Date: Sat, 30 Aug 2008 14:57:30 -0400 From: Joe Korty To: Leon Woestenberg Cc: Andrew Morton , "mingo@elte.hu" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH] shrink printk timestamp field Message-ID: <20080830185730.GA12660@tsunami.ccur.com> Reply-To: Joe Korty References: <20080827151759.GA10678@tsunami.ccur.com> <20080829163540.634e86d9.akpm@linux-foundation.org> <20080830143808.GA10821@tsunami.ccur.com> <20080830101618.b6c2e1ab.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1507 Lines: 33 On Sat, Aug 30, 2008 at 01:47:06PM -0400, Leon Woestenberg wrote: > On Sat, Aug 30, 2008 at 7:16 PM, Andrew Morton wrote: >> On Sat, 30 Aug 2008 10:38:08 -0400 Joe Korty wrote: >>> On Fri, Aug 29, 2008 at 07:35:40PM -0400, Andrew Morton wrote: >>>> On Wed, 27 Aug 2008 11:17:59 -0400 Joe Korty wrote: >>>> >>>>> Shrink the printk timestamp field. >>> >>> 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. >> >> Of course it's useful. If you're working on performance or latency in >> a disk, network or USB driver, microsecond resolution is about right. >> > I second this. If we have timestamps enables, let it be useful for all > current uses. The 3 digits extra are very cheap useful information in > that area (without resorting to more elaborate methods like the > recently merged latency tracer). > > Rather than cut 3 digits off, maybe fix some of the too-wide prints > would solve the posters issue better. > > Can we please have this patch non-committed or reverted? I have no objection... Joe -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/