| /Linux-v5.4/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 \
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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 | 73 struct drm_writeback_connector writeback; member
77 #define wb_to_rcar_crtc(c) container_of(c, struct rcar_du_crtc, writeback)
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | fuse-io.txt | 6 + 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-v5.4/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 309 writeback section in Optional Feature
319 If admin want to use incompressible page writeback, they could do via::
323 To use idle page writeback, first, user need to declare zram pages
332 Admin can request writeback of those idle pages at right timing via::
334 echo idle > /sys/block/zramX/writeback
336 With the command, zram writeback idle pages from memory to the storage.
344 any writeback. IOW, if admin want to apply writeback budget, he should
349 Once writeback_limit_enable is set, zram doesn't allow any writeback
355 If admin want to limit writeback as per-day 400M, he could do it
370 If admin want to see remaining writeback budget since he set::
[all …]
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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)
|
| /Linux-v5.4/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.
|
| /Linux-v5.4/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()
|
| /Linux-v5.4/drivers/block/ |
| D | virtio_blk.c | 587 u8 writeback; in virtblk_get_cache_mode() local
592 &writeback); in virtblk_get_cache_mode()
599 writeback = virtio_has_feature(vdev, VIRTIO_BLK_F_FLUSH); in virtblk_get_cache_mode()
601 return writeback; in virtblk_get_cache_mode()
606 u8 writeback = virtblk_get_cache_mode(vdev); in virtblk_update_cache_mode() local
609 blk_queue_write_cache(vblk->disk->queue, writeback, false); in virtblk_update_cache_mode()
641 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in cache_type_show() local
643 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in cache_type_show()
644 return snprintf(buf, 40, "%s\n", virtblk_cache_types[writeback]); in cache_type_show()
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | bcache.rst | 20 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 …]
|
| /Linux-v5.4/drivers/md/bcache/ |
| D | Makefile | 7 util.o writeback.o
|
| D | request.c | 188 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()
656 if (unlikely(s->iop.writeback && in backing_request_endio()
992 s->iop.writeback = true; in cached_dev_write()
1009 s->iop.writeback = true; in cached_dev_write()
1024 } else if (s->iop.writeback) { in cached_dev_write()
1345 s->iop.writeback = true; in flash_dev_make_request()
|
| D | request.h | 21 unsigned int writeback:1; member
|
| /Linux-v5.4/block/ |
| D | Kconfig | 119 bool "Enable support for block device writeback throttling"
122 background writeback from the VM, making it more smooth and having
149 bool "Multiqueue writeback throttling"
153 Enable writeback throttling by default on multiqueue devices.
|
| /Linux-v5.4/include/media/ |
| D | vsp1.h | 106 struct vsp1_du_writeback_config writeback; member
|
| /Linux-v5.4/drivers/iommu/ |
| D | virtio-iommu.c | 85 void *writeback; member
177 if (req->writeback && len == write_len) in __viommu_sync_req()
178 memcpy(req->writeback, req->buf + req->write_offset, in __viommu_sync_req()
219 bool writeback) in __viommu_add_req() argument
239 if (writeback) { in __viommu_add_req()
240 req->writeback = buf + write_offset; in __viommu_add_req()
|
| /Linux-v5.4/Documentation/devicetree/bindings/media/ |
| D | exynos5-gsc.txt | 16 set writeback input and destination
|
| /Linux-v5.4/mm/ |
| D | vmscan.c | 126 unsigned int writeback; member
1088 bool *dirty, bool *writeback) in page_check_dirty_writeback() argument
1099 *writeback = false; in page_check_dirty_writeback()
1105 *writeback = PageWriteback(page); in page_check_dirty_writeback()
1113 mapping->a_ops->is_dirty_writeback(page, dirty, writeback); in page_check_dirty_writeback()
1139 bool dirty, writeback; in shrink_page_list() local
1172 page_check_dirty_writeback(page, &dirty, &writeback); in shrink_page_list()
1173 if (dirty || writeback) in shrink_page_list()
1176 if (dirty && !writeback) in shrink_page_list()
1186 if (((dirty || writeback) && mapping && in shrink_page_list()
[all …]
|
| /Linux-v5.4/Documentation/media/v4l-drivers/ |
| 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
|
