From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Stefan Weinhuber <wein@linux.vnet.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Stefan Weinhuber <wein@de.ibm.com>,
Horst Hummel <Horst.Hummel@de.ibm.com>,
Stefan Haberland <stefan.haberland@de.ibm.com>,
linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: deadline ALWAYS default for dasd devices(s390) ?
Date: Thu, 06 May 2010 09:34:59 +0200 [thread overview]
Message-ID: <4BE27123.6070501@gmail.com> (raw)
In-Reply-To: <4BE123B1.1050500@linux.vnet.ibm.com>
On 05/05/2010 09:52 AM, Stefan Weinhuber wrote:
hi,
> At the time this change was made we had the problem that the
> default scheduler chosen by the distributions resulted in
> bad performance for DASD devices.
Have you done recently new cfq vs. deadline tests, in z/VM
and LPAR ?
> I agree that hard coding this choice into the driver is not pretty,
> but it is pragmatic.
It's awful. Easier and simpler from user space: /sys/block/dasdX/queue/scheduler
> Some generic mechanism for setting driver specific
> defaults would be nicer, but I doubt that many other drivers would
> actually benefit from such an interface.
see s390-tools-1.8.4/etc/udev/rules.d/60-readahead.rules
That's the way to do it.
-thanks-
--
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra;
que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie
impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor,
que no sienta mi derecho y dé pecho a mi valor.»
prev parent reply other threads:[~2010-05-06 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-26 12:34 deadline ALWAYS default for dasd devices(s390) ? Xose Vazquez Perez
2010-05-05 6:16 ` Heiko Carstens
2010-05-05 7:52 ` Stefan Weinhuber
2010-05-05 7:55 ` Michael Tokarev
2010-05-06 7:34 ` Xose Vazquez Perez [this message]
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=4BE27123.6070501@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Horst.Hummel@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=stefan.haberland@de.ibm.com \
--cc=wein@de.ibm.com \
--cc=wein@linux.vnet.ibm.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