summaryrefslogtreecommitdiff
path: root/Documentation/cpu-load.txt
diff options
context:
space:
mode:
authorJens Axboe <jaxboe@fusionio.com>2011-04-16 15:51:05 +0400
committerJens Axboe <jaxboe@fusionio.com>2011-04-16 15:51:05 +0400
commit49cac01e1fa74174d72adb0e872504a7fefd7c01 (patch)
treea1ab1974eceea3179a604413955ad8369ba715d7 /Documentation/cpu-load.txt
parenta237c1c5bc5dc5c76a21be922dca4826f3eca8ca (diff)
downloadlinux-49cac01e1fa74174d72adb0e872504a7fefd7c01.tar.xz
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>
Diffstat (limited to 'Documentation/cpu-load.txt')
0 files changed, 0 insertions, 0 deletions