From: Jens Axboe <jaxboe@fusionio.com>
To: Justin TerAvest <teravest@google.com>
Cc: "vgoyal@redhat.com" <vgoyal@redhat.com>,
"ctalbott@google.com" <ctalbott@google.com>,
"mrubin@google.com" <mrubin@google.com>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"guijianfeng@cn.fujitsu.com" <guijianfeng@cn.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Don't wait if queue already has requests.
Date: Wed, 9 Feb 2011 14:15:56 +0100 [thread overview]
Message-ID: <4D52938C.30907@fusionio.com> (raw)
In-Reply-To: <1297192697-29978-1-git-send-email-teravest@google.com>
On 2011-02-08 20:18, Justin TerAvest wrote:
> Commit 7667aa0630407bc07dc38dcc79d29cc0a65553c1 added logic to wait for
> the last queue of the group to become busy (have at least one request),
> so that the group does not lose out for not being continuously
> backlogged. The commit did not check for the condition that the last
> queue already has some requests. As a result, if the queue already has
> requests, wait_busy is set. Later on, cfq_select_queue() checks the
> flag, and decides that since the queue has a request now and wait_busy
> is set, the queue is expired. This results in early expiration of the
> queue.
>
> This patch fixes the problem by adding a check to see if queue already
> has requests. If it does, wait_busy is not set. As a result, time slices
> do not expire early.
>
> The queues with more than one request are usually buffered writers.
> Testing shows improvement in isolation between buffered writers.
Thanks for catching this in due time, I'll queue it up for 2.6.38 and
mark it for stable backport.
--
Jens Axboe
next prev parent reply other threads:[~2011-02-09 13:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 19:18 [PATCH] Don't wait if queue already has requests Justin TerAvest
2011-02-08 19:48 ` Vivek Goyal
2011-02-08 22:21 ` Justin TerAvest
2011-02-08 22:29 ` Vivek Goyal
2011-02-09 3:13 ` Gui Jianfeng
2011-02-09 13:15 ` Jens Axboe [this message]
2011-02-09 13:43 ` Jens Axboe
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=4D52938C.30907@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=ctalbott@google.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrubin@google.com \
--cc=teravest@google.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).