Home
last modified time | relevance | path

Searched refs:writeback (Results 1 – 25 of 115) sorted by relevance

12345

/linux/drivers/gpu/drm/ci/xfails/
H A Dvkms-none-fails.txt19 kms_writeback@writeback-check-output,Fail
20 kms_writeback@writeback-check-output-XRGB2101010,Fail
21 kms_writeback@writeback-fb-id,Fail
22 kms_writeback@writeback-fb-id-XRGB2101010,Fail
23 kms_writeback@writeback-invalid-parameters,Fail
24 kms_writeback@writeback-pixel-formats,Fail
/linux/drivers/gpu/drm/vkms/
H A Dvkms_config.h60 * @writeback: If true, a writeback buffer can be attached to the CRTC
70 bool writeback; member
193 * @enable_writeback: Create or not a writeback connector
322 * vkms_config_crtc_get_writeback() - If a writeback connector will be created
323 * @crtc_cfg: CRTC with or without a writeback connector
328 return crtc_cfg->writeback; in vkms_config_crtc_get_writeback()
332 * vkms_config_crtc_set_writeback() - If a writeback connector will be created
334 * @writeback: Enable or disable the writeback connecto
338 vkms_config_crtc_set_writeback(struct vkms_config_crtc * crtc_cfg,bool writeback) vkms_config_crtc_set_writeback() argument
[all...]
H A Dvkms_output.c16 int writeback; in vkms_output_init() local
46 /* Initialize the writeback component */ in vkms_output_init()
48 writeback = vkms_enable_writeback_connector(vkmsdev, crtc_cfg->crtc); in vkms_output_init()
49 if (writeback) in vkms_output_init()
50 DRM_ERROR("Failed to init writeback connector\n"); in vkms_output_init()
/linux/Documentation/admin-guide/device-mapper/
H A Dwritecache.rst27 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 Dcache.rst81 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 Dzram.rst51 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 Dabort-lv4t.S62 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/Documentation/filesystems/
H A Dfuse-io.rst12 + 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/drivers/gpu/drm/renesas/rcar-du/
H A Drcar_du_writeback.c22 * 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 Drcar_du_crtc.h45 * @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/ABI/testing/
H A Dsysfs-block-bcache7 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.
H A Dsysfs-block-zram102 What: /sys/block/zram<id>/writeback
106 The writeback file is write-only and trigger idle and/or
107 huge page writeback to backing device.
130 amount of writeback ZRAM can do. The limit could be changed
/linux/drivers/gpu/drm/ttm/
H A Dttm_backup.c72 * @writeback: Whether to perform immediate writeback of the page.
83 * deadlocking on lock_page(). If @writeback is set to true and
97 bool writeback, pgoff_t idx, gfp_t page_gfp, in ttm_backup_backup_page() argument
115 if (writeback && !folio_mapped(to_folio) && in ttm_backup_backup_page()
/linux/drivers/media/platform/renesas/vsp1/
H A Dvsp1_wpf.c220 "Failed to obtain a dl list, disabling writeback\n"); in wpf_configure_writeback_chain()
254 if (!pipe->iif && (!pipe->lif || wpf->writeback)) { in wpf_configure_stream()
351 * Configure writeback for display pipelines (the wpf writeback flag is in wpf_configure_stream()
353 * display list to disable writeback after a single frame, and process in wpf_configure_stream()
354 * to enable writeback. If the display list allocation fails don't in wpf_configure_stream()
355 * enable writeback as we wouldn't be able to safely disable it, in wpf_configure_stream()
358 if (wpf->writeback) { in wpf_configure_stream()
361 wpf->writeback = false; in wpf_configure_stream()
365 wpf->writeback in wpf_configure_stream()
[all...]
/linux/include/trace/events/
H A Dbcache.h153 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)
490 /* Background writeback */
/linux/fs/orangefs/
H A Dwaitqueue.c324 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()
338 else /* !writeback && !interruptible but compiler complains */ in wait_for_matching_downcall()
/linux/drivers/gpu/drm/xe/
H A Dxe_shrinker.c112 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/block/zram/
H A DKconfig116 With /sys/block/zramX/{idle,writeback}, application could ask
117 idle page's writeback to the backing device to save in memory.
127 pages writeback.
/linux/drivers/gpu/drm/amd/display/dc/dml2/dml21/inc/bounding_boxes/
H A Ddcn4_soc_bb.h49 .writeback = {
175 .writeback = {
/linux/fs/btrfs/
H A Dcompression.h65 /* Whether this is a write for writeback. */
66 bool writeback; member
102 bool writeback);
H A Dsubpage.c34 * 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()
461 writeback, start, len); in btrfs_subpage_clear_writeback()
466 if (subpage_test_bitmap_all_zero(fs_info, folio, writeback)) { in btrfs_subpage_clear_writeback()
553 IMPLEMENT_BTRFS_SUBPAGE_TEST_OP(writeback);
649 IMPLEMENT_BTRFS_PAGE_OPS(writeback, folio_start_writeback, folio_end_writeback,
791 GET_SUBPAGE_BITMAP(fs_info, folio, writeback, in btrfs_subpage_dump_bitmap()
[all...]
/linux/drivers/md/bcache/
H A Drequest.c14 #include "writeback.h"
176 if (op->writeback) in bch_data_insert_endio()
224 op->writeback)) in CLOSURE_CALLBACK()
232 if (op->writeback) { in CLOSURE_CALLBACK()
255 /* bch_alloc_sectors() blocks if s->writeback = true */ in CLOSURE_CALLBACK()
256 BUG_ON(op->writeback); in CLOSURE_CALLBACK()
259 * But if it's not a writeback write we'd rather just bail out if in CLOSURE_CALLBACK()
293 * be from a normal write, or a writeback write, or a write to a flash only
313 op->writeback, op->bypass); in CLOSURE_CALLBACK()
660 * If a bio has REQ_PREFLUSH for writeback mod in backing_request_endio()
[all...]
H A DMakefile7 util.o writeback.o features.o
H A Drequest.h21 unsigned int writeback:1; member
/linux/Documentation/admin-guide/
H A Dbcache.rst23 Both writethrough and writeback caching are supported. Writeback defaults to
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
413 Can be one of either writethrough, writeback, writearoun
[all...]

12345