From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, dmilburn@redhat.com
Subject: Re: [patch] Revert "block: remove artifical max_hw_sectors cap"
Date: Thu, 30 Jul 2015 06:51:34 -0700 [thread overview]
Message-ID: <20150730135134.GA14734@infradead.org> (raw)
In-Reply-To: <x49k2tihpnr.fsf@segfault.boston.devel.redhat.com>
Hi Jeff,
thanks for the detailed numbers!
The bigger I/O size makes a drastic impact for Linux software RAID
setups, for which this was a driver. For the RAID5/6 over SATA disks
setups that I was benchmarking this it gives between 20 and 40% better
sequential read and write numbers.
Besides those I've tested it on various SSDs where it didn't make any
difference, e.g. on the laptop with a Samsung 840 Evo I'm currently
travelling with and your fio script.
First line max_sectors_kb = 512, second line
max_sectors_kb = max_hw_sectors_kb (32767)
Run status group 0 (all jobs):
WRITE: io=1024.0MB, aggrb=471270KB/s, minb=471270KB/s, maxb=471270KB/s, mint=2225msec, maxt=2225msec
WRITE: io=1024.0MB, aggrb=475976KB/s, minb=475976KB/s, maxb=475976KB/s, mint=2203msec, maxt=2203msec
Run status group 1 (all jobs):
WRITE: io=1024.0MB, aggrb=477276KB/s, minb=477276KB/s, maxb=477276KB/s, mint=2197msec, maxt=2197msec
WRITE: io=1024.0MB, aggrb=479677KB/s, minb=479677KB/s, maxb=479677KB/s, mint=2186msec, maxt=2186msec
Run status group 2 (all jobs):
WRITE: io=1024.0MB, aggrb=488618KB/s, minb=488618KB/s, maxb=488618KB/s, mint=2146msec, maxt=2146msec
WRITE: io=1024.0MB, aggrb=489302KB/s, minb=489302KB/s, maxb=489302KB/s, mint=2143msec, maxt=2143msec
next prev parent reply other threads:[~2015-07-30 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 19:17 [patch] Revert "block: remove artifical max_hw_sectors cap" Jeff Moyer
2015-07-20 20:24 ` Jens Axboe
2015-07-20 20:44 ` Jeff Moyer
2015-07-21 13:02 ` Christoph Hellwig
2015-07-29 16:52 ` Jeff Moyer
2015-07-30 0:25 ` Elliott, Robert (Server Storage)
2015-07-30 14:03 ` Jeff Moyer
2015-07-30 14:03 ` Jeff Moyer
2015-07-30 13:51 ` Christoph Hellwig [this message]
2015-07-30 14:08 ` Jeff Moyer
2015-08-10 17:23 ` Jeff Moyer
2015-08-11 14:28 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2015-07-20 19:17 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=20150730135134.GA14734@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dmilburn@redhat.com \
--cc=jmoyer@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.