Searched refs:writethrough (Results 1 – 13 of 13) sorted by relevance
/linux-6.6.21/Documentation/admin-guide/device-mapper/ |
D | cache.rst | 81 The cache has three operating modes: writeback, writethrough and 88 If writethrough is selected then a write to a cached block will not 102 writethrough or writeback mode while still warm. Otherwise, the cache 192 feature args writethrough or passthrough (The default is writeback.) 206 writethrough write through caching that prohibits cache block 270 feature args 'writethrough' (optional)
|
D | dm-ima.rst | 348 … <cache_device> "," <cache_origin_device> "," <writethrough> "," <writeback> "," 357 writethrough := "writethrough=" <yes_no> 371 …cache_metadata_device=253:4,cache_device=253:3,cache_origin_device=253:5,writethrough=y,writeback=… 589 journal_dev_mode_str := "writethrough" | "writeback" | "invalid"
|
D | era.rst | 92 - Cache returns to writeback/writethrough mode
|
D | dm-raid.rst | 205 The journal device is used as writethrough thus causing writes to 212 (see 'journal_dev <dev>' above) to 'writethrough' or 'writeback'.
|
/linux-6.6.21/Documentation/ABI/testing/ |
D | sysfs-block-bcache | 65 writethrough mode; reads and writes will be added to the 75 writes transparently revert to writethrough mode. Intended only
|
/linux-6.6.21/Documentation/admin-guide/ |
D | bcache.rst | 23 Both writethrough and writeback caching are supported. Writeback defaults to 138 - For writethrough writes, if the write to the cache errors we just switch to 206 If your cache is in writethrough mode, then you can safely discard the 413 Can be one of either writethrough, writeback, writearound or none.
|
/linux-6.6.21/Documentation/filesystems/ |
D | 9p.rst | 89 0b00000100 writeback behavior (as opposed to writethrough)
|
/linux-6.6.21/arch/arm/mm/ |
D | Kconfig | 574 ARM Architecture Version 4 TLB with writethrough cache. 834 Say Y here to use the data cache in writethrough mode. Unless you 989 Say Y here to use the Feroceon L2 cache in writethrough mode.
|
/linux-6.6.21/arch/m68k/ |
D | Kconfig.cpu | 424 here will force supervisor (kernel) accesses to use writethrough
|
/linux-6.6.21/fs/fuse/ |
D | file.c | 1320 goto writethrough; in fuse_cache_write_iter() 1326 writethrough: in fuse_cache_write_iter()
|
/linux-6.6.21/drivers/md/ |
D | Kconfig | 333 cleaned etc. It supports writeback and writethrough modes.
|
/linux-6.6.21/arch/arm/boot/compressed/ |
D | head.S | 1012 .word 0x41807200 @ ARM720T (writethrough)
|
/linux-6.6.21/fs/smb/server/ |
D | smb2pdu.c | 6531 bool writethrough = false, is_rdma_channel = false; in smb2_write() local 6596 writethrough = true; in smb2_write() 6611 writethrough, &nbytes); in smb2_write() 6619 writethrough); in smb2_write()
|