| /linux/drivers/gpu/drm/ci/xfails/ |
| H A D | vkms-none-fails.txt | 19 kms_writeback@writeback-check-output,Fail 20 kms_writeback@writeback-check-output-XRGB2101010,Fail 21 kms_writeback@writeback-fb-id,Fail 22 kms_writeback@writeback-fb-id-XRGB2101010,Fail 23 kms_writeback@writeback-invalid-parameters,Fail 24 kms_writeback@writeback-pixel-formats,Fail
|
| /linux/Documentation/admin-guide/blockdev/ |
| H A D | zram.rst | 51 and writeback simultaneously). 218 writeback operations 219 compressed_writeback RW show and set compressed writeback feature 326 not used pages). This feature is useful for e.g. zram writeback and 342 writeback section in Optional Feature 352 If admin wants to use incompressible page writeback, they could do it via:: 354 echo huge > /sys/block/zramX/writeback 356 Admin can request writeback of idle pages at right timing via:: 358 echo idle > /sys/block/zramX/writeback 360 With the command, zram will writeback idle pages from memory to the storage. [all …]
|
| /linux/drivers/gpu/drm/vkms/ |
| H A D | vkms_config.h | 73 bool writeback; member 358 return crtc_cfg->writeback; in vkms_config_crtc_get_writeback() 368 bool writeback) in vkms_config_crtc_set_writeback() argument 370 crtc_cfg->writeback = writeback; in vkms_config_crtc_set_writeback()
|
| H A D | vkms_output.c | 17 int writeback; in vkms_output_init() local 45 writeback = vkms_enable_writeback_connector(vkmsdev, crtc_cfg->crtc); in vkms_output_init() 46 if (writeback) in vkms_output_init()
|
| H A D | vkms_configfs.c | 140 bool writeback; in crtc_writeback_show() local 145 writeback = vkms_config_crtc_get_writeback(crtc->config); in crtc_writeback_show() 147 return sprintf(page, "%d\n", writeback); in crtc_writeback_show() 154 bool writeback; in crtc_writeback_store() local 158 if (kstrtobool(page, &writeback)) in crtc_writeback_store() 165 vkms_config_crtc_set_writeback(crtc->config, writeback); in crtc_writeback_store() 171 CONFIGFS_ATTR(crtc_, writeback);
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A 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
|
| H A D | dm-pcache.rst | 32 …pcache <cache_dev> <backing_dev> [<number_of_optional_arguments> <cache_mode writeback> <data_crc … 40 ``cache_mode`` Optional, Only ``writeback`` is accepted at the 56 … "0 $(blockdev --getsz /dev/sdb) pcache /dev/pmem0 /dev/sdb 4 cache_mode writeback data_crc true" 184 … "0 $(blockdev --getsz /dev/sdb) pcache /dev/pmem0 /dev/sdb 4 cache_mode writeback data_crc true"
|
| H A 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/arch/arm/mm/ |
| H A 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/Documentation/filesystems/fuse/ |
| H A 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/drivers/gpu/drm/renesas/rcar-du/ |
| H A 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()
|
| H A 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/Documentation/ABI/testing/ |
| H A 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.
|
| H A D | sysfs-block-zram | 102 What: /sys/block/zram<id>/writeback 106 The writeback file is write-only and trigger idle and/or 107 huge page writeback to backing device. 130 amount of writeback ZRAM can do. The limit could be changed 159 writeback feature. 166 number of in-flight writeback operations.
|
| /linux/drivers/media/platform/renesas/vsp1/ |
| H A D | vsp1_wpf.c | 254 if (!pipe->iif && (!pipe->lif || wpf->writeback)) { in wpf_configure_stream() 358 if (wpf->writeback) { in wpf_configure_stream() 361 wpf->writeback = false; in wpf_configure_stream() 365 wpf->writeback ? VI6_WPF_WRBCK_CTRL_WBMD : 0); in wpf_configure_stream() 431 if (pipe->lif && !wpf->writeback) in wpf_configure_partition() 525 wpf->writeback = false; in wpf_configure_partition()
|
| /linux/include/trace/events/ |
| H A 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/drivers/gpu/drm/ttm/ |
| H A D | ttm_backup.c | 97 bool writeback, pgoff_t idx, gfp_t page_gfp, in ttm_backup_backup_page() argument 115 if (writeback && !folio_mapped(to_folio) && in ttm_backup_backup_page()
|
| /linux/fs/orangefs/ |
| H A 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/drivers/gpu/drm/xe/ |
| H A D | xe_shrinker.c | 112 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 D | bcache.rst | 22 Both writethrough and writeback caching are supported. Writeback defaults to 42 in the cache it first disables writeback caching and waits for all dirty data 110 important if you have writeback caching turned on. 141 - For writeback writes, we currently pass that error back up to the 146 writeback mode). It currently doesn't do anything intelligent if it fails to 167 Note that this may cause data loss if you were running in writeback mode. 344 running in writeback mode, which isn't the default (not due to a lack of 345 maturity, but simply because in writeback mode you'll lose data if something 348 # echo writeback > /sys/block/bcache0/bcache/cache_mode 412 Can be one of either writethrough, writeback, writearound or none. [all …]
|
| /linux/drivers/block/zram/ |
| H A D | Kconfig | 116 With /sys/block/zramX/{idle,writeback}, application could ask 117 idle page's writeback to the backing device to save in memory. 127 pages writeback.
|
| /linux/drivers/md/bcache/ |
| H A 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() 1311 s->iop.writeback = true; in flash_dev_submit_bio()
|
| /linux/Documentation/filesystems/iomap/ |
| H A D | operations.rst | 32 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 257 because writeback will not consume the reservation. 267 to the same region and triggers writeback to flush the dirty data out to 315 writeback. 319 ``->writeback_range`` machinery described below even if the writeback fails. 363 If this succeeds, iomap_finish_folio_write() must be called once writeback 364 completes for the range, regardless of whether the writeback succeeded or [all …]
|
| /linux/Documentation/filesystems/ |
| H A D | netfs_library.rst | 18 - Inode writeback. 41 takes over the normal buffered read, readahead, write and writeback and also 117 * For writeback, it is unknown how much there will be to write until the 164 special value (``NETFS_FOLIO_COPY_TO_CACHE``) and left to writeback to write. 168 When writeback occurs, folios that are so marked will only be written to the 256 writeback thing. 323 Netfslib will pin resources on an inode for future writeback (such as pinning 334 2) This flag then cleared inside the inode lock during inode writeback in the 414 On all three write functions, there is a writeback group pointer (which should 417 a different group, it is flushed first. The writeback API allows writing back [all …]
|
| /linux/drivers/gpu/drm/amd/display/dc/dml2_0/dml21/inc/bounding_boxes/ |
| H A D | dcn4_soc_bb.h | 48 .writeback = { 174 .writeback = {
|