mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aaron Carroll <aaronc@cse.unsw.edu.au>
To: 谢纲 <xiegang112@gmail.com>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: The difference of request dir between AS and Deadline I/O 	scheduler?
Date: Tue, 03 Mar 2009 15:58:23 +1100	[thread overview]
Message-ID: <49ACB8EF.4000600@cse.unsw.edu.au> (raw)
In-Reply-To: <d364733c0903022052g671a07ayf4ded2014d085fdf@mail.gmail.com>

谢纲 wrote:
> On Tue, Mar 3, 2009 at 12:21 PM, Aaron Carroll <aaronc@cse.unsw.edu.au> wrote:
>> � wrote:
>>> Hi,
>>>
>>> I'm little confused about the defination of request dir in AS and
>>> Deadline I/O scheduler.
>>> In AS, the request dir is defined by wheher it's sync:
>>>
>>> data_dir = rq_is_sync(rq);
>>>
>>> But in Deadline, the requests are grouped by read and write.
>>>
>>> Why is there the difference since AS is an extension of Deadline?
>>> what's the consideration?
>> I also thought it was silly to have different behaviours, so I tried
>> the following patch that makes deadline use sync/async instead of
>> read/write.  All the benchmarks I tried showed that performance
>> dropped or remained constant at best, so I didn't propose it.
>> Maybe you will have more luck...
> Hello,
> Which benchmark tool do you use? I'd like to have a try. I think the
> I/O behavior is an important factor which can affect the performance.

I can't find the original results, but from memory I tried FIO (many
random readers with various I/O sizes), postmark, and compilebench
on a single-disk and 10-disk hardware RAID system.


    -- Aaron

      reply	other threads:[~2009-03-03  5:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  5:06 谢纲
2009-03-02 12:25 ` Jens Axboe
2009-03-02 13:03   ` 谢纲
2009-03-02 13:13     ` Jens Axboe
2009-03-03  4:21 ` Aaron Carroll
2009-03-03  4:52   ` 谢纲
2009-03-03  4:58     ` Aaron Carroll [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=49ACB8EF.4000600@cse.unsw.edu.au \
    --to=aaronc@cse.unsw.edu.au \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xiegang112@gmail.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®