Lines Matching +full:cache +full:- +full:block

2 Explicit volatile write back cache control
6 ------------
10 operating system before data actually has hit the non-volatile storage.  This
12 system needs to force data out to the non-volatile storage when it performs
15 The Linux block layer provides two simple mechanisms that let filesystems
17 a forced cache flush, and the Force Unit Access (FUA) flag for requests.
20 Explicit cache flushes
21 ----------------------
24 the filesystem and will make sure the volatile cache of the storage device
26 guarantees that previously completed write requests are on non-volatile
28 set on an otherwise empty bio structure, which causes only an explicit cache
30 the blkdev_issue_flush() helper for a pure cache flush.
34 ------------------
38 signaled after the data has been committed to non-volatile storage.
42 --------------------------------------
45 worry if the underlying devices need any explicit cache flushing and how
49 Feature settings for block drivers
50 ----------------------------------
53 support required, the block layer completes empty REQ_PREFLUSH requests before
57 For devices with volatile write caches the driver needs to tell the block layer
63 bit the block layer needs to be told to pass on the REQ_FUA bit by also setting
70 Implementation details for bio based block drivers
71 --------------------------------------------------
85 Implementation details for blk-mq drivers
86 -----------------------------------------
90 request followed by the actual write by the block layer.
93 REQ_OP_WRITE request, else a REQ_OP_FLUSH request is sent by the block layer