Messages in this thread | | | Date | Sat, 6 Sep 2008 20:24:38 +0200 | From | Ingo Molnar <> | Subject | Re: [PATCH] shrink printk timestamp field |
| |
* Joe Korty <joe.korty@ccur.com> wrote:
> >> 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...
ok, i've zapped it from tip/core/printk.
Ingo
| |