Home
last modified time | relevance | path

Searched refs:writeback (Results 1 – 25 of 68) sorted by relevance

123

/Linux-v4.19/Documentation/device-mapper/
Dwritecache.txt21 start writeback when the number of used blocks reach this
24 stop writeback when the number of used blocks drops below
28 writeback. Setting this value reduces writeback
53 4. the number of blocks under writeback
Dcache.txt74 The cache has three operating modes: writeback, writethrough and
77 If writeback, the default, is selected then a write to a block that is
95 writethrough or writeback mode while still warm. Otherwise, the cache
106 importance if writeback mode is used. Writethrough and passthrough
109 warm and in writeback mode during resize.
182 feature args : writethrough or passthrough (The default is writeback.)
305 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
307 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
/Linux-v4.19/arch/arm/mm/
Dabort-lv4t.S62 tst r8, #1 << 21 @ check writeback bit
63 beq do_DataAbort @ no writeback -> no fixup
87 tst r8, #1 << 21 @ Check writeback bit
88 beq do_DataAbort @ No writeback -> no fixup
107 tst r8, #1 << 21 @ check writeback bit
108 beq do_DataAbort @ no writeback -> no fixup
123 tst r8, #1 << 21 @ check writeback bit
124 beq do_DataAbort @ no writeback -> no fixup
/Linux-v4.19/Documentation/filesystems/
Dfuse-io.txt6 + writeback-cache
20 writeback-cache mode may be selected by the FUSE_WRITEBACK_CACHE flag in the
28 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
30 fast. Dirty pages are written back implicitly (background writeback or page
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-block-bcache7 writeback mode is automatically disabled and all dirty data is
59 What: /sys/block/<disk>/bcache/writeback
63 For backing devices: When on, writeback caching is enabled and
82 For backing devices: In writeback mode, when dirty data is
84 backing device, writeback from cache to backing device starts
91 For backing devices: If nonzero, writeback from cache to
107 writeback caching enabled.
/Linux-v4.19/include/trace/events/
Dbcache.h153 bool writeback, bool bypass),
154 TP_ARGS(c, inode, bio, writeback, bypass),
162 __field(bool, writeback )
172 __entry->writeback = writeback;
179 __entry->nr_sector, __entry->writeback, __entry->bypass)
/Linux-v4.19/drivers/block/
Dvirtio_blk.c517 u8 writeback; in virtblk_get_cache_mode() local
522 &writeback); in virtblk_get_cache_mode()
529 writeback = virtio_has_feature(vdev, VIRTIO_BLK_F_FLUSH); in virtblk_get_cache_mode()
531 return writeback; in virtblk_get_cache_mode()
536 u8 writeback = virtblk_get_cache_mode(vdev); in virtblk_update_cache_mode() local
539 blk_queue_write_cache(vblk->disk->queue, writeback, false); in virtblk_update_cache_mode()
572 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in virtblk_cache_type_show() local
574 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in virtblk_cache_type_show()
575 return snprintf(buf, 40, "%s\n", virtblk_cache_types[writeback]); in virtblk_cache_type_show()
/Linux-v4.19/block/
DKconfig143 bool "Enable support for block device writeback throttling"
147 background writeback from the VM, making it more smooth and having
165 bool "Single queue writeback throttling"
169 Enable writeback throttling by default on legacy single queue devices
172 bool "Multiqueue writeback throttling"
176 Enable writeback throttling by default on multiqueue devices.
/Linux-v4.19/Documentation/admin-guide/
Dbcache.rst20 Both writethrough and writeback caching are supported. Writeback defaults to
40 in the cache it first disables writeback caching and waits for all dirty data
104 important if you have writeback caching turned on.
135 - For writeback writes, we currently pass that error back up to the
140 writeback mode). It currently doesn't do anything intelligent if it fails to
161 Note that this may cause data loss if you were running in writeback mode.
338 running in writeback mode, which isn't the default (not due to a lack of
339 maturity, but simply because in writeback mode you'll lose data if something
342 # echo writeback > /sys/block/bcache0/bcache/cache_mode
406 Can be one of either writethrough, writeback, writearound or none.
[all …]
Dcgroup-v2.rst1416 written asynchronously to the backing filesystem by the writeback
1422 implements control of page cache writeback IOs. The memory controller
1429 cgroup writeback requires explicit support from the underlying
1430 filesystem. Currently, cgroup writeback is implemented on ext2, ext4
1431 and btrfs. On other filesystems, all writeback IOs are attributed to
1434 There are inherent differences in memory and writeback management
1436 page while writeback per inode. For the purpose of writeback, an
1442 associated with. These are called foreign pages. The writeback
1453 doesn't update it until the page is released, even if writeback
1458 The sysctl knobs which affect writeback behavior are applied to cgroup
[all …]
/Linux-v4.19/drivers/md/bcache/
DMakefile7 util.o writeback.o
Drequest.c188 if (op->writeback) in bch_data_insert_endio()
236 op->writeback)) in bch_data_insert_start()
244 if (op->writeback) { in bch_data_insert_start()
268 BUG_ON(op->writeback); in bch_data_insert_start()
325 op->writeback, op->bypass); in bch_data_insert()
654 if (unlikely(s->iop.writeback && in backing_request_endio()
974 s->iop.writeback = true; in cached_dev_write()
991 s->iop.writeback = true; in cached_dev_write()
1006 } else if (s->iop.writeback) { in cached_dev_write()
1324 s->iop.writeback = true; in flash_dev_make_request()
Drequest.h21 unsigned int writeback:1; member
/Linux-v4.19/mm/
Dvmscan.c124 unsigned int writeback; member
1065 bool *dirty, bool *writeback) in page_check_dirty_writeback() argument
1076 *writeback = false; in page_check_dirty_writeback()
1082 *writeback = PageWriteback(page); in page_check_dirty_writeback()
1090 mapping->a_ops->is_dirty_writeback(page, dirty, writeback); in page_check_dirty_writeback()
1122 bool dirty, writeback; in shrink_page_list() local
1156 page_check_dirty_writeback(page, &dirty, &writeback); in shrink_page_list()
1157 if (dirty || writeback) in shrink_page_list()
1160 if (dirty && !writeback) in shrink_page_list()
1170 if (((dirty || writeback) && mapping && in shrink_page_list()
[all …]
DMakefile36 maccess.o page_alloc.o page-writeback.o \
/Linux-v4.19/Documentation/devicetree/bindings/media/
Dexynos5-gsc.txt16 set writeback input and destination
Dsamsung-fimc.txt88 writeback input.
90 writeback input.
/Linux-v4.19/Documentation/media/v4l-drivers/
Dfimc.rst11 data from LCD controller (FIMD) through the SoC internal writeback data
14 availability, LCD writeback support, etc. The driver is located at
36 - LCD writeback input
/Linux-v4.19/Documentation/core-api/
Dmm-api.rst74 .. kernel-doc:: mm/page-writeback.c
/Linux-v4.19/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt48 The main feature of POHMELFS is writeback data and the metadata cache.
52 the server during system writeback. Only one writer at a time is allowed for any
/Linux-v4.19/include/linux/
Dnfs_fs_sb.h140 atomic_long_t writeback; /* number of writeback pages */ member
Dregset.h194 user_regset_writeback_fn *writeback; member
Dpage-flags.h314 TESTPAGEFLAG(Writeback, writeback, PF_NO_TAIL) in PAGEFLAG()
315 TESTSCFLAG(Writeback, writeback, PF_NO_TAIL) in PAGEFLAG()
/Linux-v4.19/Documentation/filesystems/ext4/
Dext4.rst62 data=writeback' can be faster for some workloads. (Note however that
63 running mounted with data=writeback can potentially leave stale data
145 data=writeback Data ordering is not preserved, data may be written
372 * writeback mode
374 In data=writeback mode, ext4 does not journal data at all. This mode provides
386 mode performs slightly slower than writeback but significantly faster than
452 max_writeback_mb_bump The maximum number of megabytes the writeback
/Linux-v4.19/fs/
DMakefile13 seq_file.o xattr.o libfs.o fs-writeback.o \

123