dasd: do not force use of deadline IO scheduler
On 2008-03-04 8:52:10, Martin Schwidefsky wrote:
a bit old.
Quoted 21 lines · Josef 'Jeff' Sipek
Quoted 20 lines
Signed-off-by Josef 'Jeff' Sipek <[email protected]>--- drivers/s390/block/dasd.c | 9 --------- 1 files changed, 0 insertions(+), 9 deletions(-)drivers/s390/block/dasd.c +0
-2@@ -1946,21 +1946,12 @@ static void do_dasd_request(struct request_queue *queue)*/ static int dasd_alloc_queue (struct dasd_block *block) { -int rc; - block->request_queue =blk_init_queue (do_dasd_request, &block->request_queue_lock);if (block->request_queue ==NULL )return -ENOMEM ;
Quoted 15 lines
drivers/s390/block/dasd.c static void do_dasd_request(struct request_queue *queue) · line 1956
Quoted 10 lines
drivers/s390/block/dasd.c +0
-7block->request_queue->queuedata = block; - -elevator_exit (block->request_queue->elevator); - rc =elevator_init (block->request_queue,"deadline" ); -if (rc) { -blk_cleanup_queue (block->request_queue); -return rc; - }return 0 ; }Um, why? We have a reason to force the deadline scheduler, our performance test have shown that the deadline scheduler get the highest throughout out of the storage subsystems which are used with the machines.
Are there recent tests, cfq vs. deadline, with current kernels?
This FCP/SCSI test is a bit old(2005-03-16), and cfq vs. deadline shows no differences:
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_res_dasd_ioScheduler.html
Any DASD test out there ?
-thanks-
Signature · 4 lines
�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.�