From: Jens Axboe <jaxboe@fusionio.com>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@kernel.org" <stable@kernel.org>,
"dk@in-telegence.net" <dk@in-telegence.net>,
"tj@kernel.org" <tj@kernel.org>
Subject: Re: [PATCH] blk-thrttole: Do not use kblockd workqueue for throtl work
Date: Mon, 28 Feb 2011 12:32:08 -0500 [thread overview]
Message-ID: <4D6BDC18.7020205@fusionio.com> (raw)
In-Reply-To: <1298908305-12032-1-git-send-email-vgoyal@redhat.com>
On 2011-02-28 10:51, Vivek Goyal wrote:
> 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.
Not good, that's definitely a bug. I'll queue this up for 2.6.38.
--
Jens Axboe
prev parent reply other threads:[~2011-02-28 17:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 15:51 [PATCH] blk-thrttole: Do not use kblockd workqueue for throtl work Vivek Goyal
2011-02-28 15:56 ` Tejun Heo
2011-02-28 17:32 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D6BDC18.7020205@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=dk@in-telegence.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.