[patch 8/12] s390: enable write barriers in the dasd driver.
From: Stefan Weinhuber <[email protected]>
The DASD device driver never reorders the I/O requests and relies on
the hardware to write all data to nonvolatile storage before signaling
a successful write. Hence, the only thing we have to do to support
write barriers is to set the queue ordered flag.
Signed-off-by: Martin Schwidefsky <[email protected]>
diffstat:
drivers/s390/block/dasd.c | 1 +
1 files changed, 1 insertion(+)
diff -urpN linux-2.6/drivers/s390/block/dasd.c linux-2.6-patched/drivers/s390/block/dasd.c
--- linux-2.6/drivers/s390/block/dasd.c 2005-04-22 15:45:04.000000000 +0200
+++ linux-2.6-patched/drivers/s390/block/dasd.c 2005-04-22 15:45:04.000000000 +0200
@@ -1635,6 +1635,7 @@ dasd_setup_queue(struct dasd_device * de
blk_queue_max_hw_segments(device->request_queue, -1L);
blk_queue_max_segment_size(device->request_queue, -1L);
blk_queue_segment_boundary(device->request_queue, -1L);
+ blk_queue_ordered(device->request_queue, 1);
}
/*
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
