From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>,
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: Tue, 11 Aug 2015 07:28:12 -0700 [thread overview]
Message-ID: <20150811142812.GA17958@infradead.org> (raw)
In-Reply-To: <x49bnefrra3.fsf@segfault.boston.devel.redhat.com>
On Mon, Aug 10, 2015 at 01:23:48PM -0400, Jeff Moyer wrote:
> Unfortunately, I'm unable to reproduce your results (though my test
> setup uses SAS disks, not SATA). I tried with a 10 data disk md RAID5,
> with 32k and 128k chunk sizes. I modified the fio program to read/write
> multiples of the stripe width, and I also used aio-stress over a range
> of queue depth and I/O sizes for read, write, random read and random
> write. I didn't see any measurable performance difference. Do you
> still have access to your test setup?
Unfortuntately I don't have access to a large RAID setup at the moment.
> What do you think about reinstituting the artificial max_sectors_kb cap,
> but bumping the default up from 512KB to 1280KB? I had our performance
> team run numbers on their test setup (which is a 12 disk raid0 with 32k
> chunk size, fwiw) with max_sectors_kb set to 1280 and, aside from one
> odd data point, things looked good.
Let's settle on that for 4.2 and then look it in more detail.
>
> Cheers,
> Jeff
---end quoted text---
next prev parent reply other threads:[~2015-08-11 14:28 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
2015-08-10 17:23 ` Jeff Moyer
2015-08-11 14:28 ` Christoph Hellwig [this message]
-- 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=20150811142812.GA17958@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome