Home
last modified time | relevance | path

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

1234

/linux/Documentation/admin-guide/device-mapper/
H A Dwritecache.rst27 start writeback when the number of used blocks reach this
30 stop writeback when the number of used blocks drops below
34 writeback. Setting this value reduces writeback
60 writes) and it will gradually writeback any cached
74 pause writeback if there was some write I/O redirected to
82 4. the number of blocks under writeback
H A Dcache.rst81 The cache has three operating modes: writeback, writethrough and
84 If writeback, the default, is selected then a write to a block that is
102 writethrough or writeback mode while still warm. Otherwise, the cache
113 importance if writeback mode is used. Writethrough and passthrough
116 warm and in writeback mode during resize.
192 feature args writethrough or passthrough (The default is writeback.)
334 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
336 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
/linux/Documentation/admin-guide/blockdev/
H A Dzram.rst51 and writeback simultaneously).
324 not used pages). This feature is useful for e.g. zram writeback and
340 writeback section in Optional Feature
350 If admin wants to use incompressible page writeback, they could do it via::
352 echo huge > /sys/block/zramX/writeback
354 Admin can request writeback of idle pages at right timing via::
356 echo idle > /sys/block/zramX/writeback
358 With the command, zram will writeback idle pages from memory to the storage.
360 Additionally, if a user choose to writeback only huge and idle pages
363 echo huge_idle > /sys/block/zramX/writeback
[all …]
/linux/arch/arm/mm/
H A 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/Documentation/filesystems/
H A Dfuse-io.rst12 + writeback-cache
27 writeback-cache mode may be selected by the FUSE_WRITEBACK_CACHE flag in the
35 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
37 fast. Dirty pages are written back implicitly (background writeback or page
/linux/drivers/gpu/drm/renesas/rcar-du/
H A Drcar_du_writeback.c203 struct drm_writeback_connector *wb_conn = &rcrtc->writeback; in rcar_du_writeback_init()
225 state = rcrtc->writeback.base.state; in rcar_du_writeback_setup()
240 drm_writeback_queue_job(&rcrtc->writeback, state); in rcar_du_writeback_setup()
245 drm_writeback_signal_completion(&rcrtc->writeback, 0); in rcar_du_writeback_complete()
H A Drcar_du_crtc.h75 struct drm_writeback_connector writeback; member
79 #define wb_to_rcar_crtc(c) container_of(c, struct rcar_du_crtc, writeback)
/linux/Documentation/ABI/testing/
H A 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/include/trace/events/
H A 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/fs/orangefs/
H A Dwaitqueue.c324 int writeback = flags & ORANGEFS_OP_WRITEBACK, in wait_for_matching_downcall() local
333 if (writeback) in wait_for_matching_downcall()
335 else if (!writeback && interruptible) in wait_for_matching_downcall()
/linux/drivers/gpu/drm/xe/
H A Dxe_shrinker.c112 save_flags.writeback = false; in xe_shrinker_walk()
128 if (flags.writeback) { in xe_shrinker_walk()
212 .writeback = !ctx.no_wait_gpu && (sc->gfp_mask & __GFP_IO), in xe_shrinker_scan()
/linux/Documentation/admin-guide/
H A Dbcache.rst23 Both writethrough and writeback caching are supported. Writeback defaults to
43 in the cache it first disables writeback caching and waits for all dirty data
111 important if you have writeback caching turned on.
142 - For writeback writes, we currently pass that error back up to the
147 writeback mode). It currently doesn't do anything intelligent if it fails to
168 Note that this may cause data loss if you were running in writeback mode.
345 running in writeback mode, which isn't the default (not due to a lack of
346 maturity, but simply because in writeback mode you'll lose data if something
349 # echo writeback > /sys/block/bcache0/bcache/cache_mode
413 Can be one of either writethrough, writeback, writearound or none.
[all …]
/linux/drivers/gpu/drm/amd/display/dc/dml2/dml21/inc/bounding_boxes/
H A Ddcn4_soc_bb.h49 .writeback = {
175 .writeback = {
/linux/fs/btrfs/
H A Dcompression.h66 bool writeback; member
102 bool writeback);
H A Dsubpage.c446 writeback, start, len); in btrfs_subpage_set_writeback()
478 writeback, start, len); in btrfs_subpage_clear_writeback()
483 if (subpage_test_bitmap_all_zero(fs_info, folio, writeback)) { in btrfs_subpage_clear_writeback()
570 IMPLEMENT_BTRFS_SUBPAGE_TEST_OP(writeback);
666 IMPLEMENT_BTRFS_PAGE_OPS(writeback, folio_start_writeback, folio_end_writeback,
808 GET_SUBPAGE_BITMAP(fs_info, folio, writeback, &writeback_bitmap); in btrfs_subpage_dump_bitmap()
/linux/Documentation/filesystems/iomap/
H A Doperations.rst32 mapping, managing uptodate and dirty state, or writeback of pagecache
95 can take folio locks, fault on userspace pages, initiate writeback
103 For the pagecache, races can happen if writeback doesn't take
109 fsdax does not need this revalidation because there's no writeback
214 because writeback will not consume the reservation.
224 to the same region and triggers writeback to flush the dirty data out to
272 writeback.
276 ``->writeback_range`` machinery described below even if the writeback fails.
321 - ``writeback_submit``: Submit the previous built writeback context.
324 File systems can optionall to hook into writeback bio submission.
[all …]
/linux/drivers/md/bcache/
H A DMakefile7 util.o writeback.o features.o
H A Drequest.h21 unsigned int writeback:1; member
/linux/include/drm/ttm/
H A Dttm_backup.h63 bool writeback, pgoff_t idx, gfp_t page_gfp,
/linux/include/media/
H A Dvsp1.h99 * struct vsp1_du_writeback_config - VSP writeback configuration parameters
113 * @writeback: writeback configuration
117 struct vsp1_du_writeback_config writeback;
108 struct vsp1_du_writeback_config writeback; global() member
/linux/drivers/media/platform/renesas/vsp1/
H A Dvsp1_rwpf.h64 bool writeback; member
/linux/Documentation/admin-guide/media/
H A Dfimc.rst13 data from LCD controller (FIMD) through the SoC internal writeback data
16 availability, LCD writeback support, etc. The driver is located at
38 - LCD writeback input
/linux/arch/m68k/include/asm/
H A Dmac_via.h260 extern void via_l2_flush(int writeback);
/linux/Documentation/translations/zh_CN/core-api/
H A Dmm-api.rst83 mm/page-writeback.c
/linux/drivers/block/
H A Dvirtio_blk.c1064 u8 writeback; in virtblk_get_cache_mode() local
1069 &writeback); in virtblk_get_cache_mode()
1076 writeback = virtio_has_feature(vdev, VIRTIO_BLK_F_FLUSH); in virtblk_get_cache_mode()
1078 return writeback; in virtblk_get_cache_mode()
1118 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in cache_type_show() local
1120 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in cache_type_show()
1121 return sysfs_emit(buf, "%s\n", virtblk_cache_types[writeback]); in cache_type_show()

1234