Home
last modified time | relevance | path

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

/linux-4.4.14/arch/arm/mm/
Dabort-lv4t.S58 tst r8, #1 << 21 @ check writeback bit
59 beq do_DataAbort @ no writeback -> no fixup
81 tst r8, #1 << 21 @ Check writeback bit
82 beq do_DataAbort @ No writeback -> no fixup
99 tst r8, #1 << 21 @ check writeback bit
100 beq do_DataAbort @ no writeback -> no fixup
113 tst r8, #1 << 21 @ check writeback bit
114 beq do_DataAbort @ no writeback -> no fixup
Dproc-arm1026.S409 mov r0, #4 @ explicitly disable writeback
DKconfig544 ARM Architecture Version 4 TLB with writeback cache.
549 ARM Architecture Version 4 TLB with writeback cache and invalidate
560 Faraday ARM FA526 architecture, unified TLB with writeback cache
892 Unless you specifically require this, say N for writeback mode.
/linux-4.4.14/Documentation/ABI/testing/
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.
Dsysfs-fs-ext497 The maximum number of megabytes the writeback code will
/linux-4.4.14/Documentation/cgroups/
Dblkio-controller.txt382 written asynchronously to the backing filesystem by the writeback
388 controllers cannot be established making it impossible for writeback
390 writeback IOs are attributed to the root cgroup.
393 and the filesystem supports cgroup writeback, writeback operations
398 and enforces the more restrictive of the two. Also, writeback control
401 to their current writeback bandwidth.
404 granularity between memory controller and writeback. While memory
405 controller tracks ownership per page, writeback operates on inode
406 basis. cgroup writeback bridges the gap by tracking ownership by
411 This is a conscious design choice as writeback operations are
[all …]
Dunified-hierarchy.txt449 writeback without involving block layer.
Dmemory.txt497 writeback - # of bytes of file/anon cache that are queued for syncing to
/linux-4.4.14/Documentation/
Dbcache.txt15 Both writethrough and writeback caching are supported. Writeback defaults to
35 in the cache it first disables writeback caching and waits for all dirty data
92 important if you have writeback caching turned on.
122 - For writeback writes, we currently pass that error back up to the
127 writeback mode). It currently doesn't do anything intelligent if it fails to
139 running in writeback mode, which isn't the default (not due to a lack of
140 maturity, but simply because in writeback mode you'll lose data if something
143 # echo writeback > /sys/block/bcache0/cache_mode
205 Can be one of either writethrough, writeback, writearound or none.
262 any, waits some number of seconds before initiating writeback. Defaults to
[all …]
/linux-4.4.14/include/trace/events/
Dbcache.h152 bool writeback, bool bypass),
153 TP_ARGS(c, inode, bio, writeback, bypass),
161 __field(bool, writeback )
171 __entry->writeback = writeback;
178 __entry->nr_sector, __entry->writeback, __entry->bypass)
Dwriteback.h2 #define TRACE_SYSTEM writeback
/linux-4.4.14/drivers/block/
Dvirtio_blk.c474 u8 writeback; in virtblk_get_cache_mode() local
479 &writeback); in virtblk_get_cache_mode()
481 writeback = virtio_has_feature(vdev, VIRTIO_BLK_F_WCE); in virtblk_get_cache_mode()
483 return writeback; in virtblk_get_cache_mode()
488 u8 writeback = virtblk_get_cache_mode(vdev); in virtblk_update_cache_mode() local
491 if (writeback) in virtblk_update_cache_mode()
531 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in virtblk_cache_type_show() local
533 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in virtblk_cache_type_show()
534 return snprintf(buf, 40, "%s\n", virtblk_cache_types[writeback]); in virtblk_cache_type_show()
/linux-4.4.14/arch/mn10300/mm/
Dcache-inv-by-reg.S115 # If we are in writeback mode we check the start and end alignments,
136 # writeback mode, in which case we would be in flush and invalidate by
Dcache-inv-by-tag.S123 # If we are in writeback mode we check the start and end alignments,
/linux-4.4.14/drivers/md/bcache/
DMakefile6 util.o writeback.o
Drequest.h20 unsigned writeback:1; member
Drequest.c183 if (op->writeback) in bch_data_insert_endio()
233 op->writeback)) in bch_data_insert_start()
241 if (op->writeback) { in bch_data_insert_start()
265 BUG_ON(op->writeback); in bch_data_insert_start()
321 op->writeback, op->bypass); in bch_data_insert()
892 s->iop.writeback = true; in cached_dev_write()
909 s->iop.writeback = true; in cached_dev_write()
919 } else if (s->iop.writeback) { in cached_dev_write()
1107 s->iop.writeback = true; in flash_dev_make_request()
Dmovinggc.c107 op->writeback = KEY_DIRTY(&io->w->key); in write_moving()
/linux-4.4.14/Documentation/device-mapper/
Dcache.txt74 The cache has three operating modes: writeback, writethrough and
77 If writeback, the default, is selected then a write to a block that is
95 writethrough or writeback mode while still warm. Otherwise, the cache
106 importance if writeback mode is used. Writethrough and passthrough
109 warm and in writeback mode during resize.
187 feature args : writethrough or passthrough (The default is writeback.)
306 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
308 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
Dera.txt84 - Cache returns to writeback/writethrough mode
/linux-4.4.14/drivers/staging/lustre/
DTODO6 * Clean up CLIO layer. Lustre client readahead/writeback control needs to better
/linux-4.4.14/Documentation/DocBook/
Dfilesystems.xml.db159 API-writeback-inodes-sb-nr
160 API-writeback-inodes-sb
161 API-try-to-writeback-inodes-sb-nr
162 API-try-to-writeback-inodes-sb
D.filesystems.xml.cmd2 …fs/namei.c fs/buffer.c block/bio.c fs/seq_file.c fs/filesystems.c fs/fs-writeback.c fs/block_dev.c…
D.kernel-api.xml.cmd2 …memory.c mm/vmalloc.c mm/page_alloc.c mm/mempool.c mm/dmapool.c mm/page-writeback.c mm/truncate.c …
Dkernel-api.xml.db193 API-end-page-writeback
262 API-tag-pages-for-writeback
/linux-4.4.14/Documentation/video4linux/
Dfimc.txt9 data from LCD controller (FIMD) through the SoC internal writeback data
12 availability, LCD writeback support, etc. The driver is located at
32 - LCD writeback input
/linux-4.4.14/mm/
Dvmscan.c850 bool *dirty, bool *writeback) in page_check_dirty_writeback() argument
860 *writeback = false; in page_check_dirty_writeback()
866 *writeback = PageWriteback(page); in page_check_dirty_writeback()
874 mapping->a_ops->is_dirty_writeback(page, dirty, writeback); in page_check_dirty_writeback()
908 bool dirty, writeback; in shrink_page_list() local
942 page_check_dirty_writeback(page, &dirty, &writeback); in shrink_page_list()
943 if (dirty || writeback) in shrink_page_list()
946 if (dirty && !writeback) in shrink_page_list()
956 if (((dirty || writeback) && mapping && in shrink_page_list()
958 (writeback && PageReclaim(page))) in shrink_page_list()
DMakefile18 maccess.o page_alloc.o page-writeback.o \
Dpage-writeback.c1575 unsigned long filepages, headroom, writeback; in balance_dirty_pages() local
1582 &mdtc->dirty, &writeback); in balance_dirty_pages()
1583 mdtc->dirty += writeback; in balance_dirty_pages()
1907 unsigned long filepages, headroom, writeback; in wb_over_bg_thresh() local
1910 &writeback); in wb_over_bg_thresh()
Dmemory-failure.c775 #define writeback (1UL << PG_writeback) macro
825 #undef writeback
/linux-4.4.14/include/linux/
Dnfs_fs_sb.h133 atomic_long_t writeback; /* number of writeback pages */ member
Dpage-flags.h242 TESTPAGEFLAG(Writeback, writeback) TESTSCFLAG(Writeback, writeback) in PAGEFLAG()
Dregset.h158 user_regset_writeback_fn *writeback; member
Dbuffer_head.h145 bool *dirty, bool *writeback);
/linux-4.4.14/Documentation/filesystems/pohmelfs/
Ddesign_notes.txt48 The main feature of POHMELFS is writeback data and the metadata cache.
52 the server during system writeback. Only one writer at a time is allowed for any
/linux-4.4.14/drivers/md/
Ddm-cache-target.c365 bool writeback:1; member
1133 if (mg->writeback) { in migration_failure()
1160 if (mg->writeback) { in migration_success_pre_commit()
1202 if (mg->writeback) { in migration_success_post_commit()
1269 if (mg->writeback || mg->demote) { in issue_copy()
1376 if (mg->writeback || mg->demote) in issue_copy_or_discard()
1477 mg->writeback = false; in promote()
1493 static void writeback(struct cache *cache, struct prealloc *structs, in writeback() function
1501 mg->writeback = true; in writeback()
1527 mg->writeback = false; in demote_then_promote()
[all …]
DKconfig296 cleaned etc. It supports writeback and writethrough modes.
/linux-4.4.14/include/uapi/drm/
Dexynos_drm.h183 __u32 writeback; member
/linux-4.4.14/Documentation/filesystems/
Dext4.txt71 data=writeback' can be faster for some workloads. (Note however that
72 running mounted with data=writeback can potentially leave stale data
169 data=writeback Data ordering is not preserved, data may be written
397 * writeback mode
398 In data=writeback mode, ext4 does not journal data at all. This mode provides
409 this mode performs slightly slower than writeback but significantly faster than journal mode.
469 max_writeback_mb_bump The maximum number of megabytes the writeback
Docfs2.txt61 data=writeback Data ordering is not preserved, data may be written
Dvfs.txt538 via filemap_fdatawait_range, to wait for all writeback to
540 each page that is found to require writeback.
559 sync_page, and writepages to writeback data to storage.
768 The VM uses dirty and writeback information to determine if it needs
774 treated as dirty or writeback for the purposes of stalling.
DLocking293 ->writepages() is used for periodic writeback and for syscall-initiated
304 when the target page is marked as needing writeback. It may be called
Dporting299 of those. Caller makes sure async writeback cannot be running for the inode while
Dxfs-self-describing-metadata.txt342 already extensively verified during writeback in xfs_iflush_int, so the only
Dproc.txt909 WritebackTmp: Memory used by FUSE for temporary writeback buffers
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsamsung-fimc.txt88 writeback input.
90 writeback input.
/linux-4.4.14/fs/
DMakefile12 seq_file.o xattr.o libfs.o fs-writeback.o \
Dbuffer.c88 bool *dirty, bool *writeback) in buffer_check_dirty_writeback() argument
92 *writeback = false; in buffer_check_dirty_writeback()
100 *writeback = true; in buffer_check_dirty_writeback()
106 *writeback = true; in buffer_check_dirty_writeback()
Dbinfmt_elf.c1615 if (regset->writeback) in do_thread_regset_writeback()
1616 regset->writeback(task, regset, 1); in do_thread_regset_writeback()
/linux-4.4.14/Documentation/vm/
Dpage_migration93 2. Insure that writeback is complete.
132 15. Queued up writeback on the new page is triggered.
/linux-4.4.14/Documentation/laptops/
Dlaptop-mode.txt95 changes the dirty background ratio, so that background writeback of dirty pages
167 before a writeback is forced, while laptop mode is active. Corresponds to
173 after a forced writeback is done due to an exceeding of DIRTY_RATIO. Set
181 are disabled, and the dirty_background_ratio only determines how much writeback
260 # calls write() does its own writeback
377 # calls write() does its own writeback
/linux-4.4.14/fs/nfs/
Dfile.c503 bool *dirty, bool *writeback) in nfs_check_dirty_writeback() argument
518 *writeback = true; in nfs_check_dirty_writeback()
Dwrite.c272 if (atomic_long_inc_return(&nfss->writeback) > in nfs_set_page_writeback()
288 if (atomic_long_dec_return(&nfss->writeback) < NFS_CONGESTION_OFF_THRESH) in nfs_end_page_writeback()
1748 if (atomic_long_read(&nfss->writeback) < NFS_CONGESTION_OFF_THRESH) in nfs_commit_release_pages()
/linux-4.4.14/fs/proc/
Dtask_mmu.c1376 unsigned long writeback; member
1404 md->writeback += nr_pages; in gather_stats()
1611 if (md->writeback) in show_numa_map()
1612 seq_printf(m, " writeback=%lu", md->writeback); in show_numa_map()
/linux-4.4.14/arch/arc/kernel/
Dentry-arcv2.S129 ; either a dst of emulated LD/ST or src with address-writeback
Dentry-compact.S309 ; either a dst of emulated LD/ST or src with address-writeback
/linux-4.4.14/arch/mn10300/kernel/
Dhead.S392 # flush the local cache if it's in writeback mode
/linux-4.4.14/drivers/staging/lustre/lustre/llite/
Dvvp_dev.c424 seq_page_flag(seq, vmpage, writeback, has_flags); in vvp_pgcache_page_show()
/linux-4.4.14/Documentation/networking/
De1000.txt254 writeback. If this occurs, the driver will report a "TX Timeout" and reset
258 The improper writeback does not occur on the first descriptor in a system
/linux-4.4.14/Documentation/sysctl/
Dvm.txt123 flusher threads will start writeback.
145 will itself start writeback.
183 Setting this to zero disables periodic writeback altogether.
/linux-4.4.14/arch/m68k/mac/
Dconfig.c140 static void mac_cache_card_flush(int writeback) in mac_cache_card_flush() argument
/linux-4.4.14/arch/x86/kvm/
Demulate.c1710 static int writeback(struct x86_emulate_ctxt *ctxt, struct operand *op) in writeback() function
5276 goto writeback; in x86_emulate_insn()
5281 goto writeback; in x86_emulate_insn()
5351 writeback: in x86_emulate_insn()
5354 rc = writeback(ctxt, &ctxt->src); in x86_emulate_insn()
5359 rc = writeback(ctxt, &ctxt->dst); in x86_emulate_insn()
5469 goto writeback; in x86_emulate_insn()
Dx86.c2475 int writeback) in msr_io() argument
2502 if (writeback && copy_to_user(user_msrs->entries, entries, size)) in msr_io()
5352 bool writeback = true; in x86_emulate_instruction() local
5437 writeback = false; in x86_emulate_instruction()
5443 writeback = false; in x86_emulate_instruction()
5451 if (writeback) { in x86_emulate_instruction()
/linux-4.4.14/fs/btrfs/
Draid56.c2357 goto writeback; in finish_parity_scrub()
2421 writeback: in finish_parity_scrub()
/linux-4.4.14/fs/ceph/
Dcaps.c2770 bool writeback = false; in handle_cap_grant() local
2920 writeback = true; /* initiate writeback; will delay ack */ in handle_cap_grant()
2975 if (writeback) in handle_cap_grant()
/linux-4.4.14/drivers/gpu/drm/exynos/
Dexynos_drm_gsc.c1348 prop_list->writeback = 1; in gsc_init_prop_list()
Dexynos_drm_fimc.c1247 prop_list->writeback = 1; in fimc_init_prop_list()
/linux-4.4.14/arch/ia64/kernel/
Dptrace.c2110 .writeback = gpregs_writeback
/linux-4.4.14/Documentation/trace/
Dftrace.txt2444 echo '!writeback*:mod:ext3' >> set_ftrace_filter
/linux-4.4.14/arch/x86/
DKconfig1594 add writeback entries.