diff options
author | 2011-04-12 14:58:51 +0200 | |
---|---|---|
committer | 2011-04-12 14:58:51 +0200 | |
commit | f4af3c3d077a004762aaad052049c809fd8c6f0c (patch) | |
tree | c4cbbc37e357775fc8200e16c6eb9b3f14d30069 /tools/perf/scripts/python/check-perf-trace.py | |
parent | block: kill queue_sync_plugs() (diff) | |
download | linux-dev-f4af3c3d077a004762aaad052049c809fd8c6f0c.tar.xz linux-dev-f4af3c3d077a004762aaad052049c809fd8c6f0c.zip |
block: move queue run on unplug to kblockd
There are worries that we are now consuming a lot more stack in
some cases, since we potentially call into IO dispatch from
schedule() or io_schedule(). We can reduce this problem by moving
the running of the queue to kblockd, like the old plugging scheme
did as well.
This may or may not be a good idea from a performance perspective,
depending on how many tasks have queue plugs running at the same
time. For even the slightly contended case, doing just a single
queue run from kblockd instead of multiple runs directly from the
unpluggers will be faster.
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions