block: make unplug timer trace event correspond to the schedule() unplug
authorJens Axboe <jaxboe@fusionio.com>
Sat, 16 Apr 2011 11:51:05 +0000 (13:51 +0200)
committerJens Axboe <jaxboe@fusionio.com>
Sat, 16 Apr 2011 11:51:05 +0000 (13:51 +0200)
commit49cac01e1fa74174d72adb0e872504a7fefd7c01
treea1ab1974eceea3179a604413955ad8369ba715d7
parenta237c1c5bc5dc5c76a21be922dca4826f3eca8ca
block: make unplug timer trace event correspond to the schedule() unplug

It's a pretty close match to what we had before - the timer triggering
would mean that nobody unplugged the plug in due time, in the new
scheme this matches very closely what the schedule() unplug now is.
It's essentially the difference between an explicit unplug (IO unplug)
or an implicit unplug (timer unplug, we scheduled with pending IO
queued).

Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
block/blk-core.c
include/trace/events/block.h
kernel/trace/blktrace.c