Home
last modified time | relevance | path

Searched refs:writethrough (Results 1 – 14 of 14) sorted by relevance

/linux-6.12.1/Documentation/admin-guide/device-mapper/
Dcache.rst81 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)
Ddm-ima.rst348 … <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"
Dera.rst92 - Cache returns to writeback/writethrough mode
Ddm-raid.rst205 The journal device is used as writethrough thus causing writes to
212 (see 'journal_dev <dev>' above) to 'writethrough' or 'writeback'.
/linux-6.12.1/fs/netfs/
Dbuffered_write.c111 struct folio *folio = NULL, *writethrough = NULL; in netfs_perform_write() local
360 &writethrough); in netfs_perform_write()
385 ret2 = netfs_end_writethrough(wreq, &wbc, writethrough); in netfs_perform_write()
/linux-6.12.1/Documentation/ABI/testing/
Dsysfs-block-bcache65 writethrough mode; reads and writes will be added to the
75 writes transparently revert to writethrough mode. Intended only
/linux-6.12.1/Documentation/admin-guide/
Dbcache.rst23 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.12.1/arch/arm/mm/
DKconfig574 ARM Architecture Version 4 TLB with writethrough cache.
834 Say Y here to use the data cache in writethrough mode. Unless you
971 Say Y here to use the Feroceon L2 cache in writethrough mode.
/linux-6.12.1/Documentation/filesystems/
D9p.rst145 0b00000100 writeback behavior (as opposed to writethrough)
/linux-6.12.1/arch/m68k/
DKconfig.cpu426 here will force supervisor (kernel) accesses to use writethrough
/linux-6.12.1/fs/fuse/
Dfile.c1418 goto writethrough; in fuse_cache_write_iter()
1424 writethrough: in fuse_cache_write_iter()
/linux-6.12.1/drivers/md/
DKconfig299 cleaned etc. It supports writeback and writethrough modes.
/linux-6.12.1/arch/arm/boot/compressed/
Dhead.S1012 .word 0x41807200 @ ARM720T (writethrough)
/linux-6.12.1/fs/smb/server/
Dsmb2pdu.c6855 bool writethrough = false, is_rdma_channel = false; in smb2_write() local
6920 writethrough = true; in smb2_write()
6935 writethrough, &nbytes); in smb2_write()
6943 writethrough); in smb2_write()