Messages in this thread | | | Date | Mon, 14 Jan 2008 09:42:32 +0100 | From | Jens Axboe <> | Subject | Re: [patch] block: fix blktrace timestamps |
| |
On Mon, Jan 14 2008, Christoph Hellwig wrote: > > Folks, this is getting a little silly.
It is
> Even if CONFIG_NO_HZ is new this is a an important regression, and > yes we should avoid regressions wherever we can, and for such a quite > important feature we should fix it. On the other hand blktrace is using > the wrong interface, and it has been told multiple times on lkml that > sched_clock() should never ever be used outside the scheduler. So the > burden to fix this regression lies on the shoulders of the blktrace > maintainer.
That is true. So far alternatives have all been slower though, so not very tempting to transition to.
> No need for silly name calling here.
I don't know what thread you are reading, but neiter Ingo nor I have resorted to silly name calling. The thread has long since diverted from the original topic, though.
-- Jens Axboe
| |