| /linux-6.12.1/drivers/gpu/drm/ |
| D | drm_writeback.c | 25 * Writeback connectors are used to expose hardware which can write the output
29 * * Writeback connectors don't provide a way to output visually to the user.
31 * * Writeback connectors are visible to userspace only when the client sets
34 * * Writeback connectors don't have EDID.
36 * A framebuffer may only be attached to a writeback connector when the
41 * Unlike with planes, when a writeback framebuffer is removed by userspace DRM
43 * because no method is provided to abort a writeback operation, and in any
44 * case making a new commit whilst a writeback is ongoing is undefined (see
45 * WRITEBACK_OUT_FENCE_PTR below). As soon as the current writeback is finished,
51 * Writeback connectors have some additional properties, which userspace
[all …]
|
| /linux-6.12.1/include/linux/ |
| D | writeback.h | 3 * include/linux/writeback.h
31 * fs/fs-writeback.c
39 * A control structure which tells the writeback code what to do. These are
59 unsigned for_kupdate:1; /* A kupdate writeback */
60 unsigned for_background:1; /* A background writeback */
64 unsigned for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
68 * When writeback IOs are bounced through async layers, only the
91 struct bdi_writeback *wb; /* wb this writeback is issued under */
134 * Scale the writeback cache size proportional to the relative
138 * on page writeback completions [end_page_writeback()]. Those
[all …]
|
| D | backing-dev-defs.h | 26 WB_writeback_running, /* Writeback is in progress */
42 * why some writeback work was initiated
84 * Each wb (bdi_writeback) can perform writeback operations, is measured
85 * and throttled, independently. Without cgroup writeback, each bdi
89 * using memcg's page ownership for attributing writeback IOs, and every
112 struct list_head b_io; /* parked for writeback */
113 struct list_head b_more_io; /* parked for more writeback */
117 atomic_t writeback_inodes; /* number of inodes under writeback */
141 struct delayed_work dwork; /* work item used for writeback */
186 struct bdi_writeback wb; /* the root writeback info for this bdi */
|
| D | backing-dev.h | 16 #include <linux/writeback.h>
119 * BDI_CAP_WRITEBACK: Supports dirty page writeback, and dirty pages
121 * BDI_CAP_WRITEBACK_ACCT: Automatically account writeback pages
133 * writeback_in_progress - determine whether there is writeback in progress
136 * Determine whether there is writeback waiting to be handled against a
162 * inode_cgwb_enabled - test whether cgroup writeback is enabled on an inode
165 * Cgroup writeback requires support from the filesystem. Also, both memcg and
264 * If wbc does not have inode attached, it means cgroup writeback was in inode_to_wb_wbc()
|
| /linux-6.12.1/fs/ |
| D | fs-writeback.c | 3 * fs/fs-writeback.c
9 * pages against inodes. ie: data writeback. Writeout of the
14 * Additions for address_space-based writeback
26 #include <linux/writeback.h>
50 unsigned int for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
52 enum wb_reason reason; /* why was writeback initiated? */
81 #include <trace/events/writeback.h>
229 * The current cgroup writeback is built on the assumption that multiple
420 * folios actually under writeback. in inode_do_switch_wbs()
692 * In addition to the inodes that have completed writeback, also switch in cleanup_offline_cgwb()
[all …]
|
| /linux-6.12.1/include/drm/ |
| D | drm_writeback.h | 19 * struct drm_writeback_connector - DRM writeback connector
41 * DRM blob property data for the pixel formats list on writeback
53 * Holds a list of a connector's writeback jobs; the last item is the
90 * struct drm_writeback_job - DRM writeback job
96 * Back-pointer to the writeback connector associated with the job
118 * List item for the writeback connector's @job_queue
125 * Framebuffer to be written to by the writeback connector. Do not set
133 * Fence which will signal once the writeback has completed
|
| /linux-6.12.1/drivers/gpu/drm/renesas/rcar-du/ |
| D | rcar_du_writeback.c | 3 * R-Car Display Unit Writeback Support
22 * struct rcar_du_wb_conn_state - Driver-specific writeback connector state
24 * @format: format of the writeback framebuffer
35 * struct rcar_du_wb_job - Driver-private data for writeback jobs
183 * and can't convert to YUV separately for writeback.
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 | 45 * @writeback: the writeback connector
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/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/msm/disp/dpu1/ |
| D | dpu_hw_wb.h | 28 * @setup_outaddress: setup output address from the writeback job
29 * @setup_outformat: setup output format of writeback block from writeback job
30 * @setup_qos_lut: setup qos LUT for writeback block based on input
31 * @setup_cdp: setup chroma down prefetch block for writeback block
78 * dpu_hw_wb_init() - Initializes the writeback hw driver object.
|
| D | dpu_hw_catalog.h | 171 * @DPU_WB_LINE_MODE Writeback module supports line/linear mode
172 * @DPU_WB_BLOCK_MODE Writeback module supports block mode read
173 * @DPU_WB_CHROMA_DOWN, Writeback chroma down block,
174 * @DPU_WB_DOWNSCALE, Writeback integer downscaler,
176 * @DPU_WB_TRAFFIC_SHAPER, Writeback traffic shaper bloc
177 * @DPU_WB_UBWC, Writeback Universal bandwidth compression
178 * @DPU_WB_YUV_CONFIG Writeback supports output of YUV colorspace
179 * @DPU_WB_PIPE_ALPHA Writeback supports pipe alpha
180 * @DPU_WB_XY_ROI_OFFSET Writeback supports x/y-offset of out ROI in
182 * @DPU_WB_QOS, Writeback supports QoS control, danger/safe/creq
[all …]
|
| /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
|
| /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/mm/ |
| D | page-writeback.c | 3 * mm/page-writeback.c
24 #include <linux/writeback.h>
41 #include <trace/events/writeback.h>
65 * will look to see if it needs to force writeback or throttling.
72 * Start background writeback (via writeback threads) at this percentage
89 * The generator of dirty data starts writeback at this percentage
254 * requiring writeback.
443 * global_dirty_limits - background-writeback and dirty-throttling thresholds
871 * decide whether to put more under writeback.
882 unsigned long filepages = 0, headroom = 0, writeback = 0; in domain_dirty_avail() local
[all …]
|
| /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.
|
| /linux-6.12.1/tools/testing/selftests/cgroup/ |
| D | test_zswap.c | 252 * Attempt writeback with the following steps:
260 this will either trigger writeback if it's enabled, or reclamation
261 will fail if writeback is disabled as there isn't enough zswap space.
308 * If writeback is enabled, trying to reclaim memory now will trigger a in attempt_writeback()
309 * writeback as zswap.max is half of what was needed when reclaim ran the first time. in attempt_writeback()
310 * If writeback is disabled, memory reclaim will fail as zswap is limited and in attempt_writeback()
311 * it can't writeback to swap. in attempt_writeback()
335 /* Verify that zswap writeback occurred only if writeback was enabled */ in test_zswap_writeback_one()
349 /* Test to verify the zswap writeback path */
355 if (cg_read_strcmp(root, "memory.zswap.writeback", "1")) in test_zswap_writeback()
[all …]
|
| /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()
109 DRM_ERROR("Failed to init writeback connector\n"); in vkms_output_init()
|
| /linux-6.12.1/drivers/media/platform/renesas/vsp1/ |
| D | vsp1_wpf.c | 220 "Failed to obtain a dl list, disabling writeback\n"); in wpf_configure_writeback_chain()
251 if (!pipe->lif || wpf->writeback) { in wpf_configure_stream()
320 * Configure writeback for display pipelines (the wpf writeback flag is in wpf_configure_stream()
322 * display list to disable writeback after a single frame, and process in wpf_configure_stream()
323 * to enable writeback. If the display list allocation fails don't in wpf_configure_stream()
324 * enable writeback as we wouldn't be able to safely disable it, 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()
397 * For display pipelines without writeback enabled there's no memory in wpf_configure_partition()
[all …]
|
| /linux-6.12.1/Documentation/admin-guide/ |
| D | bcache.rst | 23 Both writethrough and writeback caching are supported. Writeback defaults to
29 Writeback caching can use most of the cache for buffering writes - writing
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
[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/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/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
258 Pagecache Writeback
268 writeback.
272 ``->map_blocks`` machinery described below even if the writeback fails.
309 - ``prepare_ioend``: Enables filesystems to transform the writeback
[all …]
|
| /linux-6.12.1/tools/writeback/ |
| D | wb_monitor.py | 7 This is a drgn script based on wq_monitor.py to monitor writeback info on
10 writeback(kB) Amount of dirty pages are currently being written back to
41 help='show writeback of bdi in cgroup')
61 'writeback' : self.stats[WB_WRITEBACK],
68 return f'{"":>16} {"writeback":>10} {"reclaimable":>12} ' \
|
| /linux-6.12.1/arch/arc/mm/ |
| D | dma.c | 41 * TO_DEV | writeback writeback | none none
43 * BIDIR | writeback+inv writeback+inv | invalidate invalidate
|
| /linux-6.12.1/include/media/ |
| D | vsp1.h | 90 * struct vsp1_du_writeback_config - VSP writeback configuration parameters
104 * @writeback: writeback configuration
108 struct vsp1_du_writeback_config writeback; member
|