| /linux/drivers/gpu/drm/ |
| H A D | drm_writeback.c | 27 * Writeback connectors are used to expose hardware which can write the output
31 * * Writeback connectors don't provide a way to output visually to the user.
33 * * Writeback connectors are visible to userspace only when the client sets
36 * * Writeback connectors don't have EDID.
38 * A framebuffer may only be attached to a writeback connector when the
43 * Unlike with planes, when a writeback framebuffer is removed by userspace DRM
45 * because no method is provided to abort a writeback operation, and in any
46 * case making a new commit whilst a writeback is ongoing is undefined (see
47 * WRITEBACK_OUT_FENCE_PTR below). As soon as the current writeback is finished,
53 * Writeback connectors have some additional properties, which userspace
[all …]
|
| /linux/include/linux/ |
| H A 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 */
63 unsigned for_sync:1; /* sync(2) WB_SYNC_ALL writeback */
67 * When writeback IOs are bounced through async layers, only the
80 struct bdi_writeback *wb; /* wb this writeback is issued under */
123 * Scale the writeback cache size proportional to the relative
127 * on page writeback completions [end_page_writeback()]. Those
[all …]
|
| H A 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 */
158 * writeback switching */
[all …]
|
| H A D | backing-dev.h | 16 #include <linux/writeback.h>
109 * BDI_CAP_WRITEBACK: Supports dirty page writeback, and dirty pages
121 * writeback_in_progress - determine whether there is writeback in progress
124 * Determine whether there is writeback waiting to be handled against a
150 * inode_cgwb_enabled - test whether cgroup writeback is enabled on an inode
153 * Cgroup writeback requires support from the filesystem. Also, both memcg and
253 * If wbc does not have inode attached, it means cgroup writeback was in inode_to_wb_wbc()
|
| /linux/fs/ |
| H A 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
419 * folios actually under writeback. in inode_do_switch_wbs()
735 * In addition to the inodes that have completed writeback, also switch in cleanup_offline_cgwb()
[all …]
|
| /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/drivers/gpu/drm/renesas/rcar-du/ |
| H A 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()
|
| H A 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/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
|
| /linux/mm/ |
| H A D | page-writeback.c | 3 * mm/page-writeback.c
24 #include <linux/writeback.h>
42 #include <trace/events/writeback.h>
66 * will look to see if it needs to force writeback or throttling.
73 * Start background writeback (via writeback threads) at this percentage
90 * The generator of dirty data starts writeback at this percentage
232 * requiring writeback.
421 * global_dirty_limits - background-writeback and dirty-throttling thresholds
855 * decide whether to put more under writeback.
866 unsigned long filepages = 0, headroom = 0, writeback = 0; in domain_dirty_avail() local
[all …]
|
| H A D | zswap.c | 33 #include <linux/writeback.h>
67 /* Load or writeback failed due to decompression failure */
150 * when a zswap_entry is taken off the lru for writeback, in that case it
182 * writeback logic. The entry is only reclaimed by the writeback
892 * of writebacks. If writeback is disabled, reject the page since it in zswap_compress()
987 * writeback code
994 * This can be thought of as a "resumed writeback" of the folio
996 * writeback path that was intercepted with the zswap_store()
1026 * shrinker. We generally writeback cold folios from zswap, and in zswap_writeback_entry()
1070 /* start writeback */ in zswap_writeback_entry()
[all …]
|
| /linux/tools/testing/selftests/cgroup/ |
| H A 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 pat
[all...] |
| /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.
|
| /linux/Documentation/admin-guide/ |
| H A 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/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/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/include/media/ |
| H A D | vsp1.h | 99 * struct vsp1_du_writeback_config - VSP writeback configuration parameters
113 * @writeback: writeback configuration
117 struct vsp1_du_writeback_config writeback;
108 struct vsp1_du_writeback_config writeback; global() member
|
| /linux/arch/arc/mm/ |
| H A D | dma.c | 41 * TO_DEV | writeback writeback | none none
43 * BIDIR | writeback+inv writeback+inv | invalidate invalidate
|
| /linux/fs/afs/ |
| H A D | write.c | 12 #include <linux/writeback.h>
31 * Find a key to use for the writeback. We cached the keys used to author the
32 * writes on the vnode. wreq->netfs_priv2 will contain the last writeback key
180 * Writeback calls this when it finds a folio that needs uploading. This isn't
181 * called if writeback only has copy-to-cache to deal with.
191 * available writeback keys.
284 * Prune the keys cached for writeback. The caller must hold vnode->wb_lock.
|
| /linux/drivers/gpu/drm/xe/ |
| H A D | xe_shrinker.c | 97 * Try shrinking idle objects without writeback first, then if not sufficient,
99 * add writeback. This avoids stalls and explicit writebacks with light or
112 save_flags.writeback = false; in xe_shrinker_walk()
128 if (flags.writeback) { in xe_shrinker_walk()
211 /* Don't request writeback without __GFP_IO. */ in xe_shrinker_scan()
212 .writeback = !ctx.no_wait_gpu && (sc->gfp_mask & __GFP_IO), in xe_shrinker_scan()
|
| /linux/Documentation/gpu/ |
| H A D | komeda-kms.rst | 46 Writeback Layer (wb_layer)
48 Writeback layer does the opposite things of Layer, which connects to compiz
73 Similar to Layer Split, but Splitter is used for writeback, which splits the
250 Writeback(output) pipeline
253 :alt: writeback digraph
254 :caption: Writeback(output) data flow
269 :alt: split writeback digraph
270 :caption: Writeback(output) Split data flow
364 - Wb_connector: `Writeback(output) pipeline`_
|
| /linux/arch/sparc/include/asm/ |
| H A D | estate.h | 18 * 2) writeback 2) copyout. The AFSR bits associated with these traps are
29 * 3) As the result of store merge completion, writeback, or copyout will
43 * during store merge, writeback, and copyout operations.
|
| /linux/fs/btrfs/ |
| H A D | subpage.h | 18 * For subpage we pack all uptodate/dirty/writeback/ordered bitmaps into
39 * delalloc can unlock its range and mark blocks writeback at random
57 * This will need a rework on the async extent lifespan (mark writeback
184 DECLARE_BTRFS_SUBPAGE_OPS(writeback);
190 * with writeback started and finished.
|
| H A D | subpage.c | 34 * The writeback is still for the full page, but we will only submit
44 * Even if we just want to writeback tree block A, we will also writeback
47 * This may cause extra metadata writeback which results more COW.
446 writeback, start, len); in btrfs_subpage_set_writeback()
453 * Don't clear the TOWRITE tag when starting writeback on a still-dirty in btrfs_subpage_set_writeback()
455 * assume writeback is complete, and exit too early — violating sync in btrfs_subpage_set_writeback()
478 writeback, start, len); in btrfs_subpage_clear_writeback()
483 if (subpage_test_bitmap_all_zero(fs_info, folio, writeback)) { in btrfs_subpage_clear_writeback()
570 IMPLEMENT_BTRFS_SUBPAGE_TEST_OP(writeback);
666 IMPLEMENT_BTRFS_PAGE_OPS(writeback, folio_start_writeback, folio_end_writeback,
[all …]
|
| /linux/arch/mips/dec/ |
| H A D | wbflush.c | 51 * For the DS3100 and DS5000/200 the R2020/R3220 writeback buffer functions
64 * For the DS5100 the writeback buffer seems to be a part of Coprocessor 3.
85 * I/O ASIC systems use a standard writeback buffer that gets flushed
|