diff options
author | Vivek Goyal <vgoyal@redhat.com> | 2011-03-01 21:40:54 +0300 |
---|---|---|
committer | Jens Axboe <jaxboe@fusionio.com> | 2011-03-01 21:41:53 +0300 |
commit | 450adcbe518ab3a3953d8475309525d22de77cba (patch) | |
tree | 352fd47d75b86804e590fd88c09f953a798ba8b0 /block/elevator.c | |
parent | 3e1f2356ce231488dc1fa844e5ce91bcb59fc2a1 (diff) | |
download | linux-450adcbe518ab3a3953d8475309525d22de77cba.tar.xz |
blk-throttle: Do not use kblockd workqueue for throtl work
o Dominik Klein reported a system hang issue while doing some blkio
throttling testing.
https://lkml.org/lkml/2011/2/24/173
o Some tracing revealed that CFQ was not dispatching any more jobs as
queue unplug was not happening. And queue unplug was not happening
because unplug work was not being called as there was one throttling
work on same cpu which as not finished yet. And throttling work had not
finished as it was tyring to dispatch a bio to CFQ but all the request
descriptors were consume to it was put to sleep.
o So basically it is a cyclic dependecny between CFQ unplug work and
throtl dispatch work. Tejun suggested that use separate workqueue for
such cases.
o This patch uses a separate workqueue for throttle related work and
does not rely on kblockd workqueue anymore.
Cc: stable@kernel.org
Reported-by: Dominik Klein <dk@in-telegence.net>
Signed-off-by: Vivek Goyal <vgoyal@redhat.com>
Acked-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'block/elevator.c')
0 files changed, 0 insertions, 0 deletions