From: Vivek Goyal <vgoyal@redhat.com>
To: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cfq-iosched: don't check cfqg in choose_service_tree()
Date: Tue, 14 Dec 2010 17:25:19 -0500 [thread overview]
Message-ID: <20101214222519.GA19693@redhat.com> (raw)
In-Reply-To: <4D070F7C.3060503@cn.fujitsu.com>
On Tue, Dec 14, 2010 at 02:32:28PM +0800, Gui Jianfeng wrote:
> When cfq_choose_cfqg() is called in select_queue(), there must be at least one
> backlogged CFQ queue waiting for dispatching, hence there must be at least one
> backlogged CFQ group on service tree. So we never call choose_service_tree()
> with cfqg == NULL.
>
> Signed-off-by: Gui Jianfeng <guijianfeng@cn.fujitsu.com>
> ---
Thanks Gui for the cleanup. This patch looks good to me.
Acked-by: Vivek Goyal <vgoyal@redhat.com>
Vivek
> block/cfq-iosched.c | 6 ------
> 1 files changed, 0 insertions(+), 6 deletions(-)
>
> diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
> index 9b186fd..c19d015 100644
> --- a/block/cfq-iosched.c
> +++ b/block/cfq-iosched.c
> @@ -2103,12 +2103,6 @@ static void choose_service_tree(struct cfq_data *cfqd, struct cfq_group *cfqg)
> unsigned group_slice;
> enum wl_prio_t original_prio = cfqd->serving_prio;
>
> - if (!cfqg) {
> - cfqd->serving_prio = IDLE_WORKLOAD;
> - cfqd->workload_expires = jiffies + 1;
> - return;
> - }
> -
> /* Choose next priority. RT > BE > IDLE */
> if (cfq_group_busy_queues_wl(RT_WORKLOAD, cfqd, cfqg))
> cfqd->serving_prio = RT_WORKLOAD;
> --
> 1.6.5.2
>
prev parent reply other threads:[~2010-12-14 22:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 6:32 [PATCH] cfq-iosched: don't check cfqg in choose_service_tree() Gui Jianfeng
2010-12-14 16:56 ` Jeff Moyer
2010-12-14 22:25 ` Vivek Goyal [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=20101214222519.GA19693@redhat.com \
--to=vgoyal@redhat.com \
--cc=axboe@kernel.dk \
--cc=guijianfeng@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
/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