diff options
| author | Jens Axboe <axboe@fb.com> | 2016-03-30 18:19:30 +0200 |
|---|---|---|
| committer | Jens Axboe <axboe@fb.com> | 2016-04-13 00:00:39 +0200 |
| commit | 2245f6de6c68b225986229a2de78c240536f7f38 (patch) | |
| tree | b0b8747993fc51d5f16239f002f089c2332ad772 /Documentation/block | |
| parent | um: switch to using blk_queue_write_cache() (diff) | |
| download | linux-2245f6de6c68b225986229a2de78c240536f7f38.tar.xz linux-2245f6de6c68b225986229a2de78c240536f7f38.zip | |
block: kill blk_queue_flush()
We don't have any drivers left using it, so kill it off. Update
documentation to use the newer blk_queue_write_cache().
Signed-off-by: Jens Axboe <axboe@fb.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'Documentation/block')
| -rw-r--r-- | Documentation/block/writeback_cache_control.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/block/writeback_cache_control.txt b/Documentation/block/writeback_cache_control.txt index 83407d36630a..59e0516cbf6b 100644 --- a/Documentation/block/writeback_cache_control.txt +++ b/Documentation/block/writeback_cache_control.txt @@ -71,7 +71,7 @@ requests that have a payload. For devices with volatile write caches the driver needs to tell the block layer that it supports flushing caches by doing: - blk_queue_flush(sdkp->disk->queue, REQ_FLUSH); + blk_queue_write_cache(sdkp->disk->queue, true, false); and handle empty REQ_FLUSH requests in its prep_fn/request_fn. Note that REQ_FLUSH requests with a payload are automatically turned into a sequence @@ -79,7 +79,7 @@ of an empty REQ_FLUSH request followed by the actual write by the block layer. For devices that also support the FUA bit the block layer needs to be told to pass through the REQ_FUA bit using: - blk_queue_flush(sdkp->disk->queue, REQ_FLUSH | REQ_FUA); + blk_queue_write_cache(sdkp->disk->queue, true, true); and the driver must handle write requests that have the REQ_FUA bit set in prep_fn/request_fn. If the FUA bit is not natively supported the block |