Searched hist:"49 cac01e1fa74174d72adb0e872504a7fefd7c01" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/include/trace/events/ |
| H A D | block.h | diff 49cac01e1fa74174d72adb0e872504a7fefd7c01 Sat Apr 16 06:51:05 CDT 2011 Jens Axboe <jaxboe@fusionio.com> 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>
|
| /openbmc/linux/kernel/trace/ |
| H A D | blktrace.c | diff 49cac01e1fa74174d72adb0e872504a7fefd7c01 Sat Apr 16 06:51:05 CDT 2011 Jens Axboe <jaxboe@fusionio.com> 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>
|
| /openbmc/linux/block/ |
| H A D | blk-core.c | diff 49cac01e1fa74174d72adb0e872504a7fefd7c01 Sat Apr 16 06:51:05 CDT 2011 Jens Axboe <jaxboe@fusionio.com> 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>
|