From: Shaohua Li <shaohua.li@intel.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jens.axboe@oracle.com" <jens.axboe@oracle.com>,
"jmoyer@redhat.com" <jmoyer@redhat.com>,
"Zhang, Yanmin" <yanmin.zhang@intel.com>
Subject: Re: cfq-iosched: tiobench regression
Date: Mon, 28 Dec 2009 10:02:03 +0800 [thread overview]
Message-ID: <20091228020203.GA28115@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <4e5e476b0912250216n2b4aceacyf22a0e73425efd3a@mail.gmail.com>
On Fri, Dec 25, 2009 at 06:16:27PM +0800, Corrado Zoccolo wrote:
> Hi Shaohua,
> On Thu, Dec 24, 2009 at 1:55 AM, Shaohua Li <shaohua.li@intel.com> wrote:
> > df5fe3e8e13883f58dc97489076bbcc150789a21
> > b3b6d0408c953524f979468562e7e210d8634150
> > The coop merge is too aggressive. For example, if two tasks are reading two
> > files where the two files have some adjecent blocks, cfq will immediately
> > merge them. cfq_rq_close() also has trouble, sometimes the seek_mean is very
> > big. I did a test to make cfq_rq_close() always checks the distence according
> > to CIC_SEEK_THR, but still saw a lot of wrong merge. (BTW, why we take a long
> > distence far away request as close. Taking them close doesn't improve any thoughtput
> > to me. Maybe we should always use CIC_SEEK_THR as close criteria).
> Yes, when deciding if two queues are going to be merged, we should use
> the constant CIC_SEEK_THR.
Ok, will prepare a seperate patch for this.
> > So sounds we need make split more aggressive. But the split is too lazay,
> > which requires to wait 1s. Time based check isn't reliable as queue might not
> > run at given time, so uses a small time isn't ok.
> 1s is too much, but I wouldn't abandon a time based approach. To fix
> the problem of queue not being run, you can consider a slice. If at
> the end of the slice, the queue is seeky, you split it.
Sounds good, will take this way.
Thanks,
Shaohua
next prev parent reply other threads:[~2009-12-28 2:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 0:55 Shaohua Li
2009-12-24 7:48 ` Gui Jianfeng
2009-12-24 9:19 ` Shaohua Li
2009-12-24 11:40 ` Corrado Zoccolo
2009-12-25 10:16 ` Corrado Zoccolo
2009-12-28 2:02 ` Shaohua Li [this message]
2009-12-28 2:03 ` [PATCH]cfq-iosched: don't take requests with long distence as close Shaohua Li
2009-12-28 8:36 ` Corrado Zoccolo
2009-12-28 8:46 ` Shaohua Li
2009-12-28 9:11 ` Corrado Zoccolo
2009-12-28 9:28 ` Shaohua Li
2009-12-28 9:40 ` Corrado Zoccolo
2009-12-28 12:16 ` Jens Axboe
2010-01-04 14:58 ` Jeff Moyer
2010-01-05 21:16 ` Jeff Moyer
2010-01-06 1:19 ` Li, Shaohua
2010-01-07 13:44 ` Corrado Zoccolo
2010-01-07 14:30 ` Jeff Moyer
2010-01-11 5:20 ` Zhang, Yanmin
2010-01-11 15:05 ` Corrado Zoccolo
2010-01-12 2:43 ` Zhang, Yanmin
2010-01-15 19:32 ` Corrado Zoccolo
2010-01-15 19:45 ` Jeff Moyer
2010-01-15 20:24 ` Corrado Zoccolo
2010-01-15 20:26 ` Jeff Moyer
2009-12-28 3:19 ` [PATCH]cfq-iosched: split seeky coop queues after one slice Shaohua Li
2009-12-28 8:40 ` Corrado Zoccolo
2009-12-28 8:52 ` Shaohua Li
2010-01-04 15:04 ` Jeff Moyer
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=20091228020203.GA28115@sli10-desk.sh.intel.com \
--to=shaohua.li@intel.com \
--cc=czoccolo@gmail.com \
--cc=jens.axboe@oracle.com \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yanmin.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®