| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_writeback.c | 24 * Writeback connectors are used to expose hardware which can write the output
28 * * Writeback connectors don't provide a way to output visually to the user.
30 * * Writeback connectors are visible to userspace only when the client sets
33 * * Writeback connectors don't have EDID.
35 * A framebuffer may only be attached to a writeback connector when the
40 * Unlike with planes, when a writeback framebuffer is removed by userspace DRM
42 * because no method is provided to abort a writeback operation, and in any
43 * case making a new commit whilst a writeback is ongoing is undefined (see
44 * WRITEBACK_OUT_FENCE_PTR below). As soon as the current writeback is finished,
50 * Writeback connectors have some additional properties, which userspace
[all …]
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | writeback.h | 3 * include/linux/writeback.h
30 * fs/fs-writeback.c
38 * A control structure which tells the writeback code what to do. These are
57 unsigned for_kupdate:1; /* A kupdate writeback */
58 unsigned for_background:1; /* A background writeback */
62 unsigned for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
66 * When writeback IOs are bounced through async layers, only the
81 struct bdi_writeback *wb; /* wb this writeback is issued under */
124 * Scale the writeback cache size proportional to the relative
128 * 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 */
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | writeback.h | 3 * include/linux/writeback.h
39 * fs/fs-writeback.c
47 * A control structure which tells the writeback code what to do. These are
66 unsigned for_kupdate:1; /* A kupdate writeback */
67 unsigned for_background:1; /* A background writeback */
71 unsigned for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
74 * When writeback IOs are bounced through async layers, only the
84 struct bdi_writeback *wb; /* wb this writeback is issued under */
133 * Scale the writeback cache size proportional to the relative
137 * on page writeback completions [end_page_writeback()]. Those
[all …]
|
| D | backing-dev-defs.h | 26 WB_writeback_running, /* Writeback is in progress */
47 * why some writeback work was initiated
89 * Each wb (bdi_writeback) can perform writeback operations, is measured
90 * and throttled, independently. Without cgroup writeback, each bdi
94 * using memcg's page ownership for attributing writeback IOs, and every
114 struct list_head b_io; /* parked for writeback */
115 struct list_head b_more_io; /* parked for more writeback */
144 struct delayed_work dwork; /* work item used for writeback */
183 struct bdi_writeback wb; /* the root writeback info for this bdi */
|
| /kernel/linux/linux-6.6/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
74 * dpu_hw_wb_init() - Initializes the writeback hw driver object.
83 * dpu_hw_wb_destroy(): Destroy writeback hw driver object.
84 * @hw_wb: Pointer to writeback hw driver object
|
| D | dpu_hw_catalog.h | 179 * @DPU_WB_LINE_MODE Writeback module supports line/linear mode
180 * @DPU_WB_BLOCK_MODE Writeback module supports block mode read
181 * @DPU_WB_CHROMA_DOWN, Writeback chroma down block,
182 * @DPU_WB_DOWNSCALE, Writeback integer downscaler,
184 * @DPU_WB_TRAFFIC_SHAPER, Writeback traffic shaper bloc
185 * @DPU_WB_UBWC, Writeback Universal bandwidth compression
186 * @DPU_WB_YUV_CONFIG Writeback supports output of YUV colorspace
187 * @DPU_WB_PIPE_ALPHA Writeback supports pipe alpha
188 * @DPU_WB_XY_ROI_OFFSET Writeback supports x/y-offset of out ROI in
190 * @DPU_WB_QOS, Writeback supports QoS control, danger/safe/creq
[all …]
|
| /kernel/linux/linux-6.6/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>
205 * The current cgroup writeback is built on the assumption that multiple
396 * folios actually under writeback. in inode_do_switch_wbs()
668 * In addition to the inodes that have completed writeback, also switch in cleanup_offline_cgwb()
[all …]
|
| /kernel/linux/linux-5.10/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>
222 * The current cgroup writeback is built on the assumption that multiple
403 * pages actually under writeback. in inode_switch_wbs_work_fn()
560 * Record @inode's writeback context into @wbc and unlock the i_lock. On
[all …]
|
| /kernel/linux/linux-5.10/include/drm/ |
| D | drm_writeback.h | 19 * struct drm_writeback_connector - DRM writeback connector
39 * DRM blob property data for the pixel formats list on writeback
51 * Holds a list of a connector's writeback jobs; the last item is the
88 * struct drm_writeback_job - DRM writeback job
94 * Back-pointer to the writeback connector associated with the job
116 * List item for the writeback connector's @job_queue
123 * Framebuffer to be written to by the writeback connector. Do not set
131 * Fence which will signal once the writeback has completed
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/fs/hmdfs/ |
| D | client_writeback.h | 26 /* writeback time limit (default 5s) */
59 /* enable hmdfs dirty writeback control */
62 /* writeback per-file inode list */
90 * writeback timelimit.
108 /* per-fs writeback work */
111 /* per-file writeback work */
115 /* per-fs writeback bandwidth */
|
| /kernel/linux/linux-6.6/fs/hmdfs/ |
| D | client_writeback.h | 26 /* writeback time limit (default 5s) */
59 /* enable hmdfs dirty writeback control */
62 /* writeback per-file inode list */
90 * writeback timelimit.
108 /* per-fs writeback work */
111 /* per-file writeback work */
115 /* per-fs writeback bandwidth */
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/rcar-du/ |
| D | rcar_du_writeback.c | 3 * rcar_du_writeback.c -- R-Car Display Unit Writeback Support
20 * struct rcar_du_wb_conn_state - Driver-specific writeback connector state
22 * @format: format of the writeback framebuffer
33 * struct rcar_du_wb_job - Driver-private data for writeback jobs
181 * and can't convert to YUV separately for writeback.
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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 309 writeback section in Optional Feature
319 If admin wants to use incompressible page writeback, they could do it via::
321 echo huge > /sys/block/zramX/writeback
323 To use idle page writeback, first, user need to declare zram pages
340 Admin can request writeback of those idle pages at right timing via::
342 echo idle > /sys/block/zramX/writeback
344 With the command, zram will writeback idle pages from memory to the storage.
346 Additionally, if a user choose to writeback only huge and idle pages
349 echo huge_idle > /sys/block/zramX/writeback
351 If a user chooses to writeback only incompressible pages (pages that none of
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/blockdev/ |
| D | zram.rst | 308 writeback section in Optional Feature
318 If admin wants to use incompressible page writeback, they could do via::
320 echo huge > /sys/block/zramX/writeback
322 To use idle page writeback, first, user need to declare zram pages
331 Admin can request writeback of those idle pages at right timing via::
333 echo idle > /sys/block/zramX/writeback
335 With the command, zram writeback idle pages from memory to the storage.
343 any writeback. IOW, if admin wants to apply writeback budget, he should
348 Once writeback_limit_enable is set, zram doesn't allow any writeback
354 If admin want to limit writeback as per-day 400M, he could do it
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-5.10/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.
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-6.6/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
252 * requiring writeback.
441 * global_dirty_limits - background-writeback and dirty-throttling thresholds
1056 * 1% by default. Without strictlimit feature, fuse writeback may in wb_position_ratio()
1557 * time, a small pool of dirty/writeback pages may go empty and disk go in wb_max_pause()
[all …]
|
| /kernel/linux/linux-6.6/drivers/media/platform/renesas/vsp1/ |
| D | vsp1_wpf.c | 222 "Failed to obtain a dl list, disabling writeback\n"); in wpf_configure_writeback_chain()
256 if (!pipe->lif || wpf->writeback) { in wpf_configure_stream()
325 * Configure writeback for display pipelines (the wpf writeback flag is in wpf_configure_stream()
327 * display list to disable writeback after a single frame, and process in wpf_configure_stream()
328 * to enable writeback. If the display list allocation fails don't in wpf_configure_stream()
329 * enable writeback as we wouldn't be able to safely disable it, in wpf_configure_stream()
332 if (wpf->writeback) { in wpf_configure_stream()
335 wpf->writeback = false; in wpf_configure_stream()
339 wpf->writeback ? VI6_WPF_WRBCK_CTRL_WBMD : 0); in wpf_configure_stream()
410 * For display pipelines without writeback enabled there's no memory in wpf_configure_partition()
[all …]
|