From: Vivek Goyal <vgoyal@redhat.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Jens Axboe <jaxboe@fusionio.com>,
czoccolo@gmail.com
Subject: Re: [patch 2/3]cfq-iosched: schedule dispatch for noidle queue
Date: Mon, 8 Nov 2010 09:28:42 -0500 [thread overview]
Message-ID: <20101108142842.GC16767@redhat.com> (raw)
In-Reply-To: <1289182038.23014.190.camel@sli10-conroe>
On Mon, Nov 08, 2010 at 10:07:18AM +0800, Shaohua Li wrote:
> A queue is idle at cfq_dispatch_requests(), but it gets noidle later. Unless
> other task explictly does unplug or all requests are drained, we will not
> deliever requests to the disk even cfq_arm_slice_timer doesn't make the
> queue idle. For example, cfq_should_idle() returns true because of
> service_tree->count == 1, and then other queues are added. Note, I didn't
> see obvious performance impacts so far with the patch, but just thought
> this could be a problem.
>
> Signed-off-by: Shaohua Li <shaohua.li@intel.com>
>
> ---
> block/cfq-iosched.c | 23 ++++++++++++++++++++++-
> 1 file changed, 22 insertions(+), 1 deletion(-)
>
> Index: linux/block/cfq-iosched.c
> ===================================================================
> --- linux.orig/block/cfq-iosched.c 2010-11-08 08:41:20.000000000 +0800
> +++ linux/block/cfq-iosched.c 2010-11-08 08:43:51.000000000 +0800
> @@ -3265,6 +3265,10 @@ cfq_should_preempt(struct cfq_data *cfqd
> if (cfq_class_rt(new_cfqq) && !cfq_class_rt(cfqq))
> return true;
>
> + /* An idle queue should not be idle now for some reason */
> + if (RB_EMPTY_ROOT(&cfqq->sort_list) && !cfq_should_idle(cfqd, cfqq))
> + return true;
> +
> if (!cfqd->active_cic || !cfq_cfqq_wait_request(cfqq))
> return false;
>
> @@ -3508,8 +3512,25 @@ static void cfq_completed_request(struct
> }
> }
>
> - if (!cfqd->rq_in_driver)
> + if (!cfqd->rq_in_driver) {
> cfq_schedule_dispatch(cfqd);
> + return;
> + }
> + /*
> + * A queue is idle at cfq_dispatch_requests(), but it gets noidle
> + * later. We schedule a dispatch if the queue has no requests,
> + * otherwise the disk is actually in idle till all requests
> + * are finished even cfq_arm_slice_timer doesn't make the queue idle
> + * */
Why do we have to wait for all requests to finish in device? Will driver
most likely not ask for next request when 1-2 requests have completed
and at that time we should expire the queue if queue is no more marked
as "noidle"?
Vivek
> + cfqq = cfqd->active_queue;
> + if (!cfqq)
> + return;
> +
> + if (RB_EMPTY_ROOT(&cfqq->sort_list) && !cfq_should_idle(cfqd, cfqq) &&
> + (!cfqd->cfq_group_idle || cfqq->cfqg->nr_cfqq > 1)) {
> + cfq_del_timer(cfqd, cfqq);
> + cfq_schedule_dispatch(cfqd);
> + }
> }
>
> /*
>
next prev parent reply other threads:[~2010-11-08 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 2:07 [patch 2/3]cfq-iosched: schedule dispatch for noidle queue Shaohua Li
2010-11-08 14:02 ` Vivek Goyal
2010-11-08 14:28 ` Vivek Goyal [this message]
2010-11-09 1:31 ` Shaohua Li
2010-11-09 2:15 ` Vivek Goyal
2010-11-09 2:26 ` Vivek Goyal
2010-11-09 2:28 ` Shaohua Li
2010-11-09 2:39 ` Vivek Goyal
2010-11-09 2:58 ` Shaohua Li
2010-11-09 13:52 ` 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=20101108142842.GC16767@redhat.com \
--to=vgoyal@redhat.com \
--cc=czoccolo@gmail.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.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.