From: Vivek Goyal <vgoyal@redhat.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [patch|rfc] add support for I/O scheduler tuning
Date: Wed, 10 Nov 2010 20:03:38 +0000 [thread overview]
Message-ID: <20101110200338.GA32733@redhat.com> (raw)
In-Reply-To: <x498w119lc5.fsf@segfault.boston.devel.redhat.com>
On Wed, Nov 10, 2010 at 01:26:21PM -0500, David Zeuthen wrote:
> Hi,
>
> On Wed, Nov 10, 2010 at 11:47 AM, Jeff Moyer <jmoyer@redhat.com> wrote:
> > Hi,
> >
> > From within the block layer in the kernel, it is difficult to
> > automatically detect the performance characteristics of the underlying
> > storage. It was suggested by Jens Axboe at LSF2010 that we write a udev
> > rule to tune the I/O scheduler properly for most cases. The basic
> > approach is to leave CFQ's default tunings alone for SATA disks. For
> > everything else, turn off slice idling and bump the quantum in order to
> > drive higher queue depths. This patch is an attempt to implement this.
> >
> > I've tested it in a variety of configurations:
> > - cciss devices
> > - sata disks
> > - sata ssds
> > - enterprise storage (single path)
> > - enterprise storage (multi-path)
> > - multiple paths to a sata disk (yes, you can actually do that!)
> >
> > The tuning works as expected in all of those scenarios. I look forward
> > to your comments.
>
> This looks useful, but I really think the kernel driver creating the
> block device should choose/change the defaults for the created block
> device - it seems really backwards to do this in user-space as an
> afterthought.
I think it just becomes little easier to implement in user space so that
if things don't work as expected, somebody can easily disable the rules
or somebody can easily refine the rule further to better suite their
needs instead of driver hardcoding this decision.
Thanks
Vivek
next prev parent reply other threads:[~2010-11-10 20:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 16:47 [patch|rfc] add support for I/O scheduler tuning Jeff Moyer
2010-11-10 17:03 ` Jeff Moyer
2010-11-10 18:26 ` David Zeuthen
2010-11-10 20:03 ` Vivek Goyal [this message]
2010-11-10 20:08 ` Jens Axboe
2010-11-11 20:07 ` Jeff Moyer
2010-11-12 14:36 ` Kay Sievers
2010-11-15 14:57 ` Vivek Goyal
2010-11-15 15:43 ` Kay Sievers
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=20101110200338.GA32733@redhat.com \
--to=vgoyal@redhat.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).