| /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()
|
| /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 | 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/Documentation/admin-guide/blockdev/ |
| H A D | zram.rst | 51 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 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/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/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/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/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/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() 1324 s->iop.writeback = true; in flash_dev_submit_bio()
|
| H A D | Makefile | 7 util.o writeback.o features.o
|
| H A D | request.h | 21 unsigned int writeback:1; member
|
| /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/include/drm/ttm/ |
| H A D | ttm_backup.h | 63 bool writeback, pgoff_t idx, gfp_t page_gfp,
|
| H A D | ttm_tt.h | 292 u32 writeback : 1; member
|
| /linux/drivers/gpu/drm/amd/display/dc/dml2_0/ |
| H A D | display_mode_core.c | 6690 …CalculateWatermarks_params->WritebackEnable = mode_lib->ms.cache_display_cfg.writeback.WritebackEn… in dml_prefetch_check() 6691 …CalculateWatermarks_params->WritebackPixelFormat = mode_lib->ms.cache_display_cfg.writeback.Writeb… in dml_prefetch_check() 6692 …CalculateWatermarks_params->WritebackDestinationWidth = mode_lib->ms.cache_display_cfg.writeback.W… in dml_prefetch_check() 6693 …CalculateWatermarks_params->WritebackDestinationHeight = mode_lib->ms.cache_display_cfg.writeback.… in dml_prefetch_check() 6694 …CalculateWatermarks_params->WritebackSourceHeight = mode_lib->ms.cache_display_cfg.writeback.Write… in dml_prefetch_check() 6897 if (mode_lib->ms.cache_display_cfg.writeback.WritebackEnable[k] == true in dml_core_mode_support() 6898 && mode_lib->ms.cache_display_cfg.writeback.WritebackPixelFormat[k] == dml_444_64) { in dml_core_mode_support() 6899 …mode_lib->ms.WriteBandwidth[k] = mode_lib->ms.cache_display_cfg.writeback.WritebackDestinationWidt… in dml_core_mode_support() 6900 * mode_lib->ms.cache_display_cfg.writeback.WritebackDestinationHeight[k] in dml_core_mode_support() 6901 / (mode_lib->ms.cache_display_cfg.writeback.WritebackSourceHeight[k] in dml_core_mode_support() [all …]
|
| /linux/drivers/media/platform/renesas/vsp1/ |
| H A D | vsp1_rwpf.h | 64 bool writeback; member
|
| /linux/Documentation/admin-guide/media/ |
| H A 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
|
| /linux/arch/m68k/include/asm/ |
| H A D | mac_via.h | 260 extern void via_l2_flush(int writeback);
|
| /linux/drivers/iommu/ |
| H A D | virtio-iommu.c | 84 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/Documentation/translations/zh_CN/core-api/ |
| H A D | mm-api.rst | 83 mm/page-writeback.c
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | starfive_starlink_pmu.rst | 40 starfive_starlink_pmu/writeback/ [Kernel PMU event]
|