Commit ff5b8cf1491330836d75eede4e5632caa32b776a
Committed by
Jens Axboe
Jens Axboe
1 parent
3e087b5754
Exists in
master
and in
20 other branches
[BLOCK] I/O barrier documentation update
Update documentation to match new barrier implementation. Signed-off-by: Tejun Heo <htejun@gmail.com> Signed-off-by: Jens Axboe <axboe@suse.de>
Showing 1 changed file with 2 additions and 8 deletions Side-by-side Diff
Documentation/block/biodoc.txt
| ... | ... | @@ -263,14 +263,8 @@ |
| 263 | 263 | The generic i/o scheduler would make sure that it places the barrier request and |
| 264 | 264 | all other requests coming after it after all the previous requests in the |
| 265 | 265 | queue. Barriers may be implemented in different ways depending on the |
| 266 | -driver. A SCSI driver for example could make use of ordered tags to | |
| 267 | -preserve the necessary ordering with a lower impact on throughput. For IDE | |
| 268 | -this might be two sync cache flush: a pre and post flush when encountering | |
| 269 | -a barrier write. | |
| 270 | - | |
| 271 | -There is a provision for queues to indicate what kind of barriers they | |
| 272 | -can provide. This is as of yet unmerged, details will be added here once it | |
| 273 | -is in the kernel. | |
| 266 | +driver. For more details regarding I/O barriers, please read barrier.txt | |
| 267 | +in this directory. | |
| 274 | 268 | |
| 275 | 269 | 1.2.2 Request Priority/Latency |
| 276 | 270 |