From: Jeff Moyer <jmoyer@redhat.com>
To: axboe@kernel.dk
Cc: linux-kernel@vger.kernel.org, Jeff Moyer <jmoyer@redhat.com>
Subject: [PATCH 2/2] cfq: allow dispatching of both sync and async I/O together
Date: Mon, 21 Jun 2010 15:49:49 -0400 [thread overview]
Message-ID: <1277149789-4493-3-git-send-email-jmoyer@redhat.com> (raw)
In-Reply-To: <1277149789-4493-1-git-send-email-jmoyer@redhat.com>
Hi,
In testing a workload that has a single fsync-ing process and another
process that does a sequential buffered read, I was unable to tune CFQ
to reach the throughput of deadline. This patch, along with the previous
one, brought CFQ in line with deadline when setting slice_idle to 0.
I'm not sure what the original reason for not allowing sync and async
I/O to be dispatched together was. If there is a workload I should be
testing that shows the inherent problems of this, please point me at it
and I will resume testing. Until and unless that workload is identified,
please consider applying this patch.
Cheers,
Jeff
Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
---
block/cfq-iosched.c | 12 ------------
1 files changed, 0 insertions(+), 12 deletions(-)
diff --git a/block/cfq-iosched.c b/block/cfq-iosched.c
index 572a050..dab836e 100644
--- a/block/cfq-iosched.c
+++ b/block/cfq-iosched.c
@@ -2296,18 +2296,6 @@ static bool cfq_may_dispatch(struct cfq_data *cfqd, struct cfq_queue *cfqq)
{
unsigned int max_dispatch;
- /*
- * Drain async requests before we start sync IO
- */
- if (cfq_should_idle(cfqd, cfqq) && cfqd->rq_in_flight[BLK_RW_ASYNC])
- return false;
-
- /*
- * If this is an async queue and we have sync IO in flight, let it wait
- */
- if (cfqd->rq_in_flight[BLK_RW_SYNC] && !cfq_cfqq_sync(cfqq))
- return false;
-
max_dispatch = max_t(unsigned int, cfqd->cfq_quantum / 2, 1);
if (cfq_class_idle(cfqq))
max_dispatch = 1;
--
1.6.5.2
next prev parent reply other threads:[~2010-06-21 19:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-21 19:49 [PATCH 0/2] cfq: fixes to bring cfq in line with deadline performance for mid- to high-end storage Jeff Moyer
2010-06-21 19:49 ` [PATCH 1/2] cfq: always return false from should_idle if slice_idle is set to zero Jeff Moyer
2010-06-21 20:00 ` Jens Axboe
2010-06-28 18:41 ` Jeff Moyer
2010-06-28 18:50 ` Jens Axboe
2010-06-28 18:54 ` Jeff Moyer
2010-06-21 23:05 ` Vivek Goyal
2010-06-21 19:49 ` Jeff Moyer [this message]
2010-06-21 19:59 ` [PATCH 2/2] cfq: allow dispatching of both sync and async I/O together Jens Axboe
2010-06-21 20:05 ` Jeff Moyer
2010-06-21 23:22 ` Vivek Goyal
2010-06-22 4:07 ` Vivek Goyal
2010-06-22 12:45 ` Jeff Moyer
2010-06-22 13:18 ` Vivek Goyal
2010-06-22 13:21 ` Jens Axboe
2010-06-22 14:24 ` Vivek Goyal
2010-06-22 14:27 ` Jeff Moyer
2010-06-28 18:40 ` Jeff Moyer
2010-06-28 18:48 ` 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=1277149789-4493-3-git-send-email-jmoyer@redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--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;
as well as URLs for NNTP newsgroup(s).