linux-kernel - Re: [patch 2/3]cfq-iosched: schedule dispatch for noidle queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1289271496.23014.213.camel@sli10-conroe>
Date:	Tue, 09 Nov 2010 10:58:16 +0800
From:	Shaohua Li <shaohua.li@...el.com>
To:	Vivek Goyal <vgoyal@...hat.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Jens Axboe <jaxboe@...ionio.com>,
	"czoccolo@...il.com" <czoccolo@...il.com>
Subject: Re: [patch 2/3]cfq-iosched: schedule dispatch for noidle queue

On Tue, 2010-11-09 at 10:39 +0800, Vivek Goyal wrote:
> On Tue, Nov 09, 2010 at 10:28:36AM +0800, Shaohua Li wrote:
> 
> [..]
> > > > > 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"?
> > > > The issue is a queue is idle just because it's the last queue of the
> > > > service tree. Then a new queue is added and the idled queue should not
> > > > idle now. we should preempt the idled queue soon. does this make sense
> > > > to you?
> > > 
> > > If that's the case then you should just modify should_preempt() so that
> > > addition of a new queue could preempt an empty queue which has now become
> > > noidle.
> > > 
> > > You have also modified cfq_completed_request() function, which will wake
> > > up the worker thread and then try to dispatch a request. IMHO, in practice
> > > driver asks for new request almost immediately and you don't gain much
> > > by this additional wakeup.
> > > 
> > > So my point being, that we increased the code complexity for no visible
> > > performance improvement also increased thread wakeups resulting in more
> > > cpu consumption.
> > Ah, you are right, we only need modify should_preempt. Updated the patch as below.
> > 
> 
> Thanks. Jens has already applied the patches on for-2.6.38/core branch of
> block tree. I think you shall have to generate an incremental patch
> which revert the bits introduced in cfq_completed_request().
Jens, how to handle this? if you want to an incremental patch, here it
is.

Subject: cfq-iosched: don't schedule a dispatch for a non-idle queue

Vivek suggests we don't need schedule a dispatch when an idle queue
becomes nonidle. And he is right, cfq_should_preempt already covers
the logic.

Signed-off-by: Shaohua Li <shaohua.li@...el.com>

---
 block/cfq-iosched.c |   19 +------------------
 1 file changed, 1 insertion(+), 18 deletions(-)

Index: linux/block/cfq-iosched.c
===================================================================
--- linux.orig/block/cfq-iosched.c	2010-11-09 10:48:08.000000000 +0800
+++ linux/block/cfq-iosched.c	2010-11-09 10:48:44.000000000 +0800
@@ -3512,25 +3512,8 @@ 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
-	 * */
-	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);
-	}
 }
 
 /*


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/