linux-kernel - Re: deadline ALWAYS default for dasd devices(s390) ?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4BE27123.6070501@gmail.com>
Date:	Thu, 06 May 2010 09:34:59 +0200
From:	Xose Vazquez Perez <xose.vazquez@...il.com>
To:	Stefan Weinhuber <wein@...ux.vnet.ibm.com>
CC:	Heiko Carstens <heiko.carstens@...ibm.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) ?

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.»
--
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/