| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 05 May 2010 09:52:17 +0200 From: Stefan Weinhuber <wein@...ux.vnet.ibm.com> To: Heiko Carstens <heiko.carstens@...ibm.com> CC: Xose Vazquez Perez <xose.vazquez@...il.com>, Stefan Weinhuber <wein@...ibm.com>, Horst Hummel <Horst.Hummel@...ibm.com>, Stefan Haberland <stefan.haberland@...ibm.com>, linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: deadline ALWAYS default for dasd devices(s390) ? Heiko Carstens 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 !!! >> > > Horst, Stefan W. or Stefan H. should be able to answer your question. 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists