From: Michael Tokarev <mjt@tls.msk.ru>
To: Stefan Weinhuber <wein@linux.vnet.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
Xose Vazquez Perez <xose.vazquez@gmail.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: Wed, 05 May 2010 11:55:11 +0400 [thread overview]
Message-ID: <4BE1245F.801@msgid.tls.msk.ru> (raw)
In-Reply-To: <4BE123B1.1050500@linux.vnet.ibm.com>
05.05.2010 11:52, Stefan Weinhuber wrote:
>> On Mon, Apr 26, 2010 at 02:34:16PM +0200, Xose Vazquez Perez wrote:
>>> hi,
>>>
>>> why is it FORCED ? bypassing a GLOBAL setting and also the kernel
>>> command line !!!
>
> 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.
> I don't know what options were considered back then, but
> I think that having the device driver set a driver specific default
> is better than forcing the whole system to use 'our' scheduler.
>
> I agree that hard coding this choice into the driver is not pretty,
> but it is pragmatic. 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 also another thread started just two days ago:
http://lkml.org/lkml/2010/5/3/404
Just... one more data point... ;)
/mjt
next prev parent reply other threads:[~2010-05-05 7:55 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 [this message]
2010-05-06 7:34 ` Xose Vazquez Perez
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=4BE1245F.801@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--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 \
--cc=xose.vazquez@gmail.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