mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeff Moyer <jmoyer@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
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 10:08:18 -0400	[thread overview]
Message-ID: <x49k2thivql.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20150730135134.GA14734@infradead.org> (Christoph Hellwig's message of "Thu, 30 Jul 2015 06:51:34 -0700")

Christoph Hellwig <hch@infradead.org> writes:

> 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.

OK, thanks for the details on the setup.  Did you try with max_sector_kb
values between 512 and 32767?  I wonder if we can find a happy middle
ground, like 1280 or even 2048.

I'll try to setup a software raid 5 with 10 disks and get back to you.
If you have a preference for the exact geometry, please speak up.

Thanks!
Jeff

  reply	other threads:[~2015-07-30 14:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 19:17 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 13:51     ` Christoph Hellwig
2015-07-30 14:08       ` Jeff Moyer [this message]
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=x49k2thivql.fsf@segfault.boston.devel.redhat.com \
    --to=jmoyer@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dmilburn@redhat.com \
    --cc=hch@infradead.org \
    --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
all inboxes | Powered by JetHome®