On Mon, 2008-03-03 at 15:21 -0500, Josef 'Jeff' Sipek wrote:
> Signed-off-by: Josef 'Jeff' Sipek <jeffpc@xxxxxxxxxxxxxx>
> ---
> drivers/s390/block/dasd.c | 9 ---------
> 1 files changed, 0 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/s390/block/dasd.c b/drivers/s390/block/dasd.c
> index ccf46c9..4d4f6ff 100644
> --- a/drivers/s390/block/dasd.c
> +++ b/drivers/s390/block/dasd.c
> @@ -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;
>
> block->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.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
