| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | writecache.rst | 28 start writeback when the number of used blocks reach this
31 stop writeback when the number of used blocks drops below
35 writeback. Setting this value reduces writeback
61 4. the number of blocks under writeback
|
| D | cache.rst | 81 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 \
|
| /kernel/linux/linux-5.10/arch/arm/mm/ |
| D | abort-lv4t.S | 62 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
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/rcar-du/ |
| D | rcar_du_writeback.c | 201 struct drm_writeback_connector *wb_conn = &rcrtc->writeback; in rcar_du_writeback_init()
223 state = rcrtc->writeback.base.state; in rcar_du_writeback_setup()
238 drm_writeback_queue_job(&rcrtc->writeback, state); in rcar_du_writeback_setup()
243 drm_writeback_signal_completion(&rcrtc->writeback, 0); in rcar_du_writeback_complete()
|
| D | rcar_du_crtc.h | 75 struct drm_writeback_connector writeback; member
79 #define wb_to_rcar_crtc(c) container_of(c, struct rcar_du_crtc, writeback)
|
| /kernel/linux/linux-5.10/Documentation/filesystems/ |
| D | fuse-io.rst | 12 + writeback-cache
26 writeback-cache mode may be selected by the FUSE_WRITEBACK_CACHE flag in the
34 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
36 fast. Dirty pages are written back implicitly (background writeback or page
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 308 writeback section in Optional Feature
318 If admin wants to use incompressible page writeback, they could do via::
320 echo huge > /sys/block/zramX/writeback
322 To use idle page writeback, first, user need to declare zram pages
331 Admin can request writeback of those idle pages at right timing via::
333 echo idle > /sys/block/zramX/writeback
335 With the command, zram writeback idle pages from memory to the storage.
343 any writeback. IOW, if admin wants to apply writeback budget, he should
348 Once writeback_limit_enable is set, zram doesn't allow any writeback
354 If admin want to limit writeback as per-day 400M, he could do it
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-block-bcache | 7 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.
|
| D | sysfs-block-zram | 110 What: /sys/block/zram<id>/writeback
114 The writeback file is write-only and trigger idle and/or
115 huge page writeback to backing device.
138 amount of writeback ZRAM can do. The limit could be changed
|
| /kernel/linux/linux-5.10/drivers/media/platform/vsp1/ |
| D | vsp1_wpf.c | 279 if (!pipe->lif || wpf->writeback) { in wpf_configure_stream()
355 if (wpf->writeback) { in wpf_configure_stream()
358 wpf->writeback = false; in wpf_configure_stream()
362 wpf->writeback ? VI6_WPF_WRBCK_CTRL_WBMD : 0); in wpf_configure_stream()
436 if (pipe->lif && !wpf->writeback) in wpf_configure_partition()
530 wpf->writeback = false; in wpf_configure_partition()
|
| D | vsp1_rwpf.h | 64 bool writeback; member
|
| /kernel/linux/linux-5.10/include/trace/events/ |
| D | bcache.h | 153 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)
|
| /kernel/linux/linux-5.10/fs/orangefs/ |
| D | waitqueue.c | 324 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()
|
| /kernel/linux/linux-5.10/drivers/block/ |
| D | virtio_blk.c | 578 u8 writeback; in virtblk_get_cache_mode() local
583 &writeback); in virtblk_get_cache_mode()
590 writeback = virtio_has_feature(vdev, VIRTIO_BLK_F_FLUSH); in virtblk_get_cache_mode()
592 return writeback; in virtblk_get_cache_mode()
597 u8 writeback = virtblk_get_cache_mode(vdev); in virtblk_update_cache_mode() local
600 blk_queue_write_cache(vblk->disk->queue, writeback, false); in virtblk_update_cache_mode()
632 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in cache_type_show() local
634 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in cache_type_show()
635 return snprintf(buf, 40, "%s\n", virtblk_cache_types[writeback]); in cache_type_show()
|
| /kernel/linux/linux-5.10/drivers/block/zram/ |
| D | Kconfig | 26 With /sys/block/zramX/{idle,writeback}, application could ask
27 idle page's writeback to the backing device to save in memory.
|
| /kernel/linux/linux-5.10/drivers/md/bcache/ |
| D | Makefile | 7 util.o writeback.o features.o
|
| D | request.c | 176 if (op->writeback) in bch_data_insert_endio()
224 op->writeback)) in bch_data_insert_start()
232 if (op->writeback) { in bch_data_insert_start()
256 BUG_ON(op->writeback); in bch_data_insert_start()
313 op->writeback, op->bypass); in bch_data_insert()
652 if (unlikely(s->iop.writeback && in backing_request_endio()
988 s->iop.writeback = true; in cached_dev_write()
1005 s->iop.writeback = true; in cached_dev_write()
1020 } else if (s->iop.writeback) { in cached_dev_write()
1310 s->iop.writeback = true; in flash_dev_submit_bio()
|
| D | request.h | 21 unsigned int writeback:1; member
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | bcache.rst | 23 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 …]
|
| /kernel/linux/linux-5.10/block/ |
| D | Kconfig | 128 bool "Enable support for block device writeback throttling"
131 background writeback from the VM, making it more smooth and having
159 bool "Multiqueue writeback throttling"
163 Enable writeback throttling by default on multiqueue devices.
|
| /kernel/linux/linux-5.10/include/media/ |
| D | vsp1.h | 106 struct vsp1_du_writeback_config writeback; member
|
| /kernel/linux/linux-5.10/drivers/iommu/ |
| D | virtio-iommu.c | 85 void *writeback; member
176 if (req->writeback && len == write_len) in __viommu_sync_req()
177 memcpy(req->writeback, req->buf + req->write_offset, in __viommu_sync_req()
218 bool writeback) in __viommu_add_req() argument
238 if (writeback) { in __viommu_add_req()
239 req->writeback = buf + write_offset; in __viommu_add_req()
|
| /kernel/linux/linux-5.10/arch/m68k/include/asm/ |
| D | mac_via.h | 260 extern void via_l2_flush(int writeback);
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | fimc.rst | 13 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/ |
| D | exynos5-gsc.txt | 16 set writeback input and destination
|