Messages in this thread | | | Date | Fri, 11 Jan 2008 10:42:05 +0100 | From | Ingo Molnar <> | Subject | Re: CONFIG_NO_HZ breaks blktrace timestamps |
| |
* Jens Axboe <jens.axboe@oracle.com> wrote:
> > they are from the scheduler git tree (except the first debug patch), > > but queued up for v2.6.25 at the moment. > > So this means that blktrace will be broken with CONFIG_NO_HZ for > 2.6.24? That's clearly a regression.
64-bit CONFIG_NO_HZ is a new feature in v2.6.24. If it happens on 32-bit too and it didnt happen in v2.6.23 32-bit then it's a regression.
all this comes from blktrace's original decision of using sched_clock() :-) It's not a global timesource and it's not trivial to turn it into a halfways usable global timesource.
Ingo
| |