/linux-6.12.1/drivers/gpu/drm/ci/xfails/ |
D | vkms-none-fails.txt | 46 kms_writeback@writeback-check-output,Fail 47 kms_writeback@writeback-check-output-XRGB2101010,Fail 48 kms_writeback@writeback-fb-id,Fail 49 kms_writeback@writeback-fb-id-XRGB2101010,Fail 50 kms_writeback@writeback-invalid-parameters,Fail 51 kms_writeback@writeback-pixel-formats,Fail
|
/linux-6.12.1/drivers/gpu/drm/vkms/ |
D | vkms_output.c | 58 int writeback; in vkms_output_init() local 106 if (vkmsdev->config->writeback) { in vkms_output_init() 107 writeback = vkms_enable_writeback_connector(vkmsdev); in vkms_output_init() 108 if (writeback) in vkms_output_init()
|
D | vkms_drv.c | 99 seq_printf(m, "writeback=%d\n", vkmsdev->config->writeback); in vkms_config_show() 251 config->writeback = enable_writeback; in vkms_init()
|
/linux-6.12.1/Documentation/admin-guide/device-mapper/ |
D | writecache.rst | 27 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
|
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-6.12.1/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-6.12.1/Documentation/admin-guide/blockdev/ |
D | zram.rst | 334 writeback section in Optional Feature 344 If admin wants to use incompressible page writeback, they could do it via:: 346 echo huge > /sys/block/zramX/writeback 348 To use idle page writeback, first, user need to declare zram pages 365 Admin can request writeback of those idle pages at right timing via:: 367 echo idle > /sys/block/zramX/writeback 369 With the command, zram will writeback idle pages from memory to the storage. 371 Additionally, if a user choose to writeback only huge and idle pages 374 echo huge_idle > /sys/block/zramX/writeback 376 If a user chooses to writeback only incompressible pages (pages that none of [all …]
|
/linux-6.12.1/Documentation/filesystems/ |
D | fuse-io.rst | 12 + 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-6.12.1/drivers/gpu/drm/renesas/rcar-du/ |
D | rcar_du_writeback.c | 203 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()
|
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)
|
/linux-6.12.1/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-6.12.1/drivers/media/platform/renesas/vsp1/ |
D | vsp1_wpf.c | 251 if (!pipe->lif || wpf->writeback) { in wpf_configure_stream() 327 if (wpf->writeback) { in wpf_configure_stream() 330 wpf->writeback = false; in wpf_configure_stream() 334 wpf->writeback ? VI6_WPF_WRBCK_CTRL_WBMD : 0); in wpf_configure_stream() 400 if (pipe->lif && !wpf->writeback) in wpf_configure_partition() 494 wpf->writeback = false; in wpf_configure_partition()
|
/linux-6.12.1/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-6.12.1/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-6.12.1/drivers/block/zram/ |
D | Kconfig | 115 With /sys/block/zramX/{idle,writeback}, application could ask 116 idle page's writeback to the backing device to save in memory. 126 pages writeback.
|
/linux-6.12.1/drivers/gpu/drm/amd/display/dc/dml2/dml21/inc/bounding_boxes/ |
D | dcn4_soc_bb.h | 49 .writeback = { 175 .writeback = {
|
D | dcn3_soc_bb.h | 69 .writeback = { 225 .writeback = {
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/drivers/md/bcache/ |
D | request.c | 176 if (op->writeback) in bch_data_insert_endio() 224 op->writeback)) in CLOSURE_CALLBACK() 232 if (op->writeback) { in CLOSURE_CALLBACK() 256 BUG_ON(op->writeback); in CLOSURE_CALLBACK() 313 op->writeback, op->bypass); in CLOSURE_CALLBACK() 666 if (unlikely(s->iop.writeback && in backing_request_endio() 997 s->iop.writeback = true; in cached_dev_write() 1014 s->iop.writeback = true; in cached_dev_write() 1029 } else if (s->iop.writeback) { in cached_dev_write() 1324 s->iop.writeback = true; in flash_dev_submit_bio()
|
D | Makefile | 7 util.o writeback.o features.o
|
D | request.h | 21 unsigned int writeback:1; member
|
/linux-6.12.1/fs/btrfs/ |
D | compression.h | 63 bool writeback; member 107 bool writeback);
|
/linux-6.12.1/Documentation/filesystems/iomap/ |
D | operations.rst | 32 mapping, managing uptodate and dirty state, or writeback of pagecache 97 can take folio locks, fault on userspace pages, initiate writeback 105 For the pagecache, races can happen if writeback doesn't take 111 fsdax does not need this revalidation because there's no writeback 210 because writeback will not consume the reservation. 220 to the same region and triggers writeback to flush the dirty data out to 268 writeback. 272 ``->map_blocks`` machinery described below even if the writeback fails. 309 - ``prepare_ioend``: Enables filesystems to transform the writeback 310 ioend or perform any other preparatory work before the writeback I/O [all …]
|
/linux-6.12.1/include/media/ |
D | vsp1.h | 108 struct vsp1_du_writeback_config writeback; member
|