| /Linux-v6.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-v6.1/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
83 struct bdi_writeback *wb; /* wb this writeback is issued under */
129 * Scale the writeback cache size proportional to the relative
133 * 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 */
183 struct bdi_writeback wb; /* the root writeback info for this bdi */
|
| D | backing-dev.h | 16 #include <linux/writeback.h>
111 * BDI_CAP_WRITEBACK: Supports dirty page writeback, and dirty pages
113 * BDI_CAP_WRITEBACK_ACCT: Automatically account writeback pages
125 * writeback_in_progress - determine whether there is writeback in progress
128 * Determine whether there is writeback waiting to be handled against a
154 * inode_cgwb_enabled - test whether cgroup writeback is enabled on an inode
157 * Cgroup writeback requires support from the filesystem. Also, both memcg and
256 * If wbc does not have inode attached, it means cgroup writeback was in inode_to_wb_wbc()
|
| /Linux-v6.1/drivers/gpu/drm/msm/disp/dpu1/ |
| D | dpu_hw_wb.h | 33 * struct dpu_hw_wb_qos_cfg : Writeback pipe QoS configuration
50 * @setup_outaddress: setup output address from the writeback job
51 * @setup_outformat: setup output format of writeback block from writeback job
52 * @setup_qos_lut: setup qos LUT for writeback block based on input
53 * @setup_cdp: setup chroma down prefetch block for writeback block
100 * dpu_hw_wb_init(): Initializes and return writeback hw driver object.
110 * dpu_hw_wb_destroy(): Destroy writeback hw driver object.
111 * @hw_wb: Pointer to writeback hw driver object
|
| D | dpu_hw_catalog.h | 222 * @DPU_WB_LINE_MODE Writeback module supports line/linear mode
223 * @DPU_WB_BLOCK_MODE Writeback module supports block mode read
224 * @DPU_WB_CHROMA_DOWN, Writeback chroma down block,
225 * @DPU_WB_DOWNSCALE, Writeback integer downscaler,
227 * @DPU_WB_TRAFFIC_SHAPER, Writeback traffic shaper bloc
228 * @DPU_WB_UBWC, Writeback Universal bandwidth compression
229 * @DPU_WB_YUV_CONFIG Writeback supports output of YUV colorspace
230 * @DPU_WB_PIPE_ALPHA Writeback supports pipe alpha
231 * @DPU_WB_XY_ROI_OFFSET Writeback supports x/y-offset of out ROI in
233 * @DPU_WB_QOS, Writeback supports QoS control, danger/safe/creq
[all …]
|
| D | dpu_encoder_phys.h | 154 * @INTR_IDX_WB_DONE: Writeback fone interrupt for virtual connector
184 * @wb_idx: Writeback index on dpu hardware
235 * @wbirq_refcount: Reference count of writeback interrupt
237 * @wb_cfg: writeback block config to store fb related details
238 * @wb_conn: backpointer to writeback connector
239 * @wb_job: backpointer to current writeback job
240 * @dest: dpu buffer layout for current writeback output buffer
280 * @wb_idx: Writeback index this phys_enc will control
322 * dpu_encoder_phys_wb_init - initialize writeback encoder
|
| D | dpu_encoder_phys_wb.c | 37 * dpu_encoder_phys_wb_set_ot_limit - set OT limit for writeback interface
61 * dpu_encoder_phys_wb_set_qos_remap - set QoS remapper for writeback
76 DPU_ERROR("invalid writeback hardware\n"); in dpu_encoder_phys_wb_set_qos_remap()
98 * dpu_encoder_phys_wb_set_qos - set QoS/danger/safe LUTs for writeback
331 * dpu_encoder_phys_wb_setup - setup writeback encoder
388 * dpu_encoder_phys_wb_done_irq - writeback interrupt handler
389 * @arg: Pointer to writeback encoder
526 * dpu_encoder_phys_wb_enable - enable writeback encoder
535 * dpu_encoder_phys_wb_disable - disable writeback encoder
571 * dpu_encoder_phys_wb_destroy - destroy writeback encoder
[all …]
|
| /Linux-v6.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>
204 * The current cgroup writeback is built on the assumption that multiple
394 * folios actually under writeback. in inode_do_switch_wbs()
687 * Record @inode's writeback context into @wbc and unlock the i_lock. On
[all …]
|
| /Linux-v6.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-v6.1/drivers/gpu/drm/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-v6.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-v6.1/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
354 echo "page_index=1251" > /sys/block/zramX/writeback
[all …]
|
| /Linux-v6.1/mm/ |
| D | page-writeback.c | 3 * mm/page-writeback.c
23 #include <linux/writeback.h>
40 #include <trace/events/writeback.h>
64 * will look to see if it needs to force writeback or throttling.
71 * Start background writeback (via writeback threads) at this percentage
88 * The generator of dirty data starts writeback at this percentage
251 * requiring writeback.
433 * global_dirty_limits - background-writeback and dirty-throttling thresholds
922 * 1% by default. Without strictlimit feature, fuse writeback may in wb_position_ratio()
1423 * time, a small pool of dirty/writeback pages may go empty and disk go in wb_max_pause()
[all …]
|
| /Linux-v6.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-v6.1/drivers/gpu/drm/vkms/ |
| D | vkms_output.c | 60 int writeback; in vkms_output_init() local
107 if (vkmsdev->config->writeback) { in vkms_output_init()
108 writeback = vkms_enable_writeback_connector(vkmsdev); in vkms_output_init()
109 if (writeback) in vkms_output_init()
110 DRM_ERROR("Failed to init writeback connector\n"); in vkms_output_init()
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | fuse-io.rst | 12 + writeback-cache
26 writeback-cache mode may be selected by the FUSE_WRITEBACK_CACHE flag in the
34 In writeback-cache mode (enabled by the FUSE_WRITEBACK_CACHE flag) writes go to
36 fast. Dirty pages are written back implicitly (background writeback or page
|
| /Linux-v6.1/drivers/media/platform/renesas/vsp1/ |
| D | vsp1_wpf.c | 245 "Failed to obtain a dl list, disabling writeback\n"); in wpf_configure_writeback_chain()
279 if (!pipe->lif || wpf->writeback) { in wpf_configure_stream()
348 * Configure writeback for display pipelines (the wpf writeback flag is in wpf_configure_stream()
350 * display list to disable writeback after a single frame, and process in wpf_configure_stream()
351 * to enable writeback. If the display list allocation fails don't in wpf_configure_stream()
352 * enable writeback as we wouldn't be able to safely disable it, in wpf_configure_stream()
355 if (wpf->writeback) { in wpf_configure_stream()
358 wpf->writeback = false; in wpf_configure_stream()
362 wpf->writeback ? VI6_WPF_WRBCK_CTRL_WBMD : 0); in wpf_configure_stream()
433 * For display pipelines without writeback enabled there's no memory in wpf_configure_partition()
[all …]
|
| /Linux-v6.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-v6.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-v6.1/drivers/md/bcache/ |
| D | writeback.c | 3 * background writeback - scan btree for dirty data and write it to the backing
13 #include "writeback.h"
94 * have an unreasonable small writeback rate at a highly fragmented situation in __update_writeback_rate()
97 * dirty data is still not even reached to writeback percent, so the rate in __update_writeback_rate()
99 * stuck at a non-writeback mode. in __update_writeback_rate()
180 * c->idle_counter is increased by writeback thread of all in idle_counter_exceeded()
210 /* Don't sst max writeback rate if it is disabled */ in set_at_max_writeback_rate()
214 /* Don't set max writeback rate if gc is running */ in set_at_max_writeback_rate()
271 * will set writeback rate to a max number. Then it is in update_writeback_rate()
272 * unncessary to update writeback rate for an idle cache set in update_writeback_rate()
[all …]
|
| D | request.c | 14 #include "writeback.h"
176 if (op->writeback) in bch_data_insert_endio()
224 op->writeback)) in bch_data_insert_start()
232 if (op->writeback) { in bch_data_insert_start()
255 /* bch_alloc_sectors() blocks if s->writeback = true */ in bch_data_insert_start()
256 BUG_ON(op->writeback); in bch_data_insert_start()
259 * But if it's not a writeback write we'd rather just bail out if in bch_data_insert_start()
293 * be from a normal write, or a writeback write, or a write to a flash only
313 op->writeback, op->bypass); in bch_data_insert()
646 * If a bio has REQ_PREFLUSH for writeback mode, it is in backing_request_endio()
[all …]
|
| /Linux-v6.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
|
| /Linux-v6.1/arch/arc/mm/ |
| D | dma.c | 41 * TO_DEV | writeback writeback | none none
43 * BIDIR | writeback+inv writeback+inv | invalidate invalidate
|
