From: Jeff Moyer <jmoyer@redhat.com>
To: Corrado Zoccolo <czoccolo@gmail.com>
Cc: Vivek Goyal <vgoyal@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>,
Shaohua Li <shaohua.li@intel.com>,
Gui Jianfeng <guijianfeng@cn.fujitsu.com>
Subject: Re: [PATCH] cfq-iosched: non-rot devices do not need read queue merging
Date: Mon, 04 Jan 2010 11:51:00 -0500 [thread overview]
Message-ID: <x49wrzxak5n.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <4e5e476b1001040836p2c8d7486x807a1a89b61c2458@mail.gmail.com> (Corrado Zoccolo's message of "Mon, 4 Jan 2010 17:36:21 +0100")
Corrado Zoccolo <czoccolo@gmail.com> writes:
> Hi Vivkek,
>
> On Mon, Jan 4, 2010 at 3:47 PM, Vivek Goyal <vgoyal@redhat.com> wrote:
>> On Wed, Dec 30, 2009 at 11:22:47PM +0100, Corrado Zoccolo wrote:
>>> Non rotational devices' performances are not affected by
>>> distance of read requests, so there is no point in having
>>> overhead to merge such queues.
>>> This doesn't apply to writes, so this patch changes the
>>> queued[] field, to be indexed by READ/WRITE instead of
>>> SYNC/ASYNC, and only compute proximity for queues with
>>> WRITE requests.
>>>
>>
>> Hi Corrado,
>>
>> What's the reason that reads don't benefit from merging queues and hence
>> merging requests and only writes do on SSD?
>
> On SSDs, reads are just limited by the maximum transfer rate, and
> larger (i.e. merged) reads will just take proportionally longer.
This is simply not true. You can get more bandwidth from an SSD (I just
checked numbers for 2 vendors' devices) by issuing larger read requests,
no matter whether the access pattern is sequential or random.
Cheers,
Jeff
next prev parent reply other threads:[~2010-01-04 16:51 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 12:10 [PATCH] cfq-iosched: non-rot devices do not need " Corrado Zoccolo
2009-12-30 18:45 ` Jens Axboe
2009-12-30 20:31 ` Corrado Zoccolo
2009-12-30 21:11 ` Jens Axboe
2009-12-30 21:21 ` Corrado Zoccolo
2009-12-30 21:34 ` Jens Axboe
2009-12-30 22:22 ` [PATCH] cfq-iosched: non-rot devices do not need read " Corrado Zoccolo
2010-01-04 14:47 ` Vivek Goyal
2010-01-04 16:36 ` Corrado Zoccolo
2010-01-04 16:51 ` Jeff Moyer [this message]
2010-01-04 18:32 ` Vivek Goyal
2010-01-04 18:37 ` Corrado Zoccolo
2010-01-04 18:51 ` Vivek Goyal
2010-01-04 19:04 ` Jeff Moyer
2010-01-04 20:37 ` Corrado Zoccolo
2010-01-05 14:58 ` Jeff Moyer
2010-01-05 15:13 ` Vivek Goyal
2010-01-05 21:19 ` Jeff Moyer
2010-01-05 21:48 ` Corrado Zoccolo
2010-01-07 10:56 ` Kirill Afonshin
2010-01-07 13:38 ` Corrado Zoccolo
2010-01-07 14:36 ` Vivek Goyal
2010-01-07 17:00 ` Corrado Zoccolo
2010-01-07 18:37 ` Vivek Goyal
2010-01-07 20:16 ` Corrado Zoccolo
2010-01-08 18:53 ` Vivek Goyal
2010-01-10 12:55 ` Corrado Zoccolo
2010-01-10 21:04 ` [PATCH] cfq-iosched: NCQ SSDs " Corrado Zoccolo
2010-01-10 21:08 ` Corrado Zoccolo
2010-01-11 11:25 ` Jeff Garzik
2010-01-11 12:26 ` Corrado Zoccolo
2010-01-11 13:13 ` Jens Axboe
2010-01-11 13:18 ` Jeff Garzik
2010-01-11 13:24 ` Jens Axboe
2010-01-11 14:53 ` Corrado Zoccolo
2010-01-11 16:44 ` Vivek Goyal
2010-01-11 17:00 ` Corrado Zoccolo
2010-01-11 17:07 ` Vivek Goyal
2010-01-11 19:05 ` Corrado Zoccolo
2010-01-11 17:11 ` Vivek Goyal
2010-01-11 19:09 ` Corrado Zoccolo
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=x49wrzxak5n.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=czoccolo@gmail.com \
--cc=guijianfeng@cn.fujitsu.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaohua.li@intel.com \
--cc=vgoyal@redhat.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®