Home
last modified time | relevance | path

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

/linux-4.1.27/arch/arm/mm/
Dabort-lv4t.S57 tst r8, #1 << 21 @ check writeback bit
58 beq do_DataAbort @ no writeback -> no fixup
80 tst r8, #1 << 21 @ Check writeback bit
81 beq do_DataAbort @ No writeback -> no fixup
98 tst r8, #1 << 21 @ check writeback bit
99 beq do_DataAbort @ no writeback -> no fixup
112 tst r8, #1 << 21 @ check writeback bit
113 beq do_DataAbort @ no writeback -> no fixup
Dproc-arm1026.S409 mov r0, #4 @ explicitly disable writeback
DKconfig548 ARM Architecture Version 4 TLB with writeback cache.
553 ARM Architecture Version 4 TLB with writeback cache and invalidate
564 Faraday ARM FA526 architecture, unified TLB with writeback cache
883 Unless you specifically require this, say N for writeback mode.
/linux-4.1.27/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.1.27/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.1.27/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.1.27/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()
484 return writeback; in virtblk_get_cache_mode()
489 u8 writeback = virtblk_get_cache_mode(vdev); in virtblk_update_cache_mode() local
492 if (writeback) in virtblk_update_cache_mode()
532 u8 writeback = virtblk_get_cache_mode(vblk->vdev); in virtblk_cache_type_show() local
534 BUG_ON(writeback >= ARRAY_SIZE(virtblk_cache_types)); in virtblk_cache_type_show()
535 return snprintf(buf, 40, "%s\n", virtblk_cache_types[writeback]); in virtblk_cache_type_show()
/linux-4.1.27/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.1.27/drivers/md/bcache/
DMakefile6 util.o writeback.o
Drequest.h20 unsigned writeback:1; member
Drequest.c180 if (op->writeback) in bch_data_insert_endio()
228 op->writeback)) in bch_data_insert_start()
236 if (op->writeback) { in bch_data_insert_start()
259 BUG_ON(op->writeback); in bch_data_insert_start()
315 op->writeback, op->bypass); in bch_data_insert()
883 s->iop.writeback = true; in cached_dev_write()
900 s->iop.writeback = true; in cached_dev_write()
910 } else if (s->iop.writeback) { in cached_dev_write()
1093 s->iop.writeback = true; in flash_dev_make_request()
Dmovinggc.c107 op->writeback = KEY_DIRTY(&io->w->key); in write_moving()
/linux-4.1.27/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.)
295 /dev/mapper/ssd /dev/mapper/origin 512 1 writeback default 0'
297 /dev/mapper/ssd /dev/mapper/origin 1024 1 writeback \
Dera.txt84 - Cache returns to writeback/writethrough mode
/linux-4.1.27/drivers/staging/lustre/
DTODO6 * Clean up CLIO layer. Lustre client readahead/writeback control needs to better
/linux-4.1.27/Documentation/DocBook/
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 …
/linux-4.1.27/Documentation/filesystems/
Dext3.txt47 data=writeback Data ordering is not preserved, data may be written
165 * writeback mode
166 In data=writeback mode, ext3 does not journal data at all. This mode provides
177 writeback but significantly faster than journal mode.
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.txt536 via filemap_fdatawait_range, to wait for all writeback to
538 each page that is found to require writeback.
557 sync_page, and writepages to writeback data to storage.
766 The VM uses dirty and writeback information to determine if it needs
772 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.txt894 WritebackTmp: Memory used by FUSE for temporary writeback buffers
/linux-4.1.27/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.1.27/fs/ext3/
DKconfig38 performance. The use of "data=writeback" can cause
50 privacy issues of data=writeback and are willing to make
/linux-4.1.27/mm/
Dvmscan.c813 bool *dirty, bool *writeback) in page_check_dirty_writeback() argument
823 *writeback = false; in page_check_dirty_writeback()
829 *writeback = PageWriteback(page); in page_check_dirty_writeback()
837 mapping->a_ops->is_dirty_writeback(page, dirty, writeback); in page_check_dirty_writeback()
871 bool dirty, writeback; in shrink_page_list() local
905 page_check_dirty_writeback(page, &dirty, &writeback); in shrink_page_list()
906 if (dirty || writeback) in shrink_page_list()
909 if (dirty && !writeback) in shrink_page_list()
919 if (((dirty || writeback) && mapping && in shrink_page_list()
921 (writeback && PageReclaim(page))) in shrink_page_list()
DMakefile18 maccess.o page_alloc.o page-writeback.o \
Dmemory-failure.c814 #define writeback (1UL << PG_writeback) macro
871 #undef writeback
DKconfig304 # initiates buffer writeback without locking the page or setting PG_writeback,
/linux-4.1.27/drivers/md/
Ddm-cache-target.c320 bool writeback:1; member
924 if (mg->writeback) { in migration_failure()
950 if (mg->writeback) { in migration_success_pre_commit()
986 if (mg->writeback) { in migration_success_post_commit()
1052 if (mg->writeback || mg->demote) { in issue_copy()
1157 if (mg->writeback || mg->demote) in issue_copy_or_discard()
1258 mg->writeback = false; in promote()
1274 static void writeback(struct cache *cache, struct prealloc *structs, in writeback() function
1282 mg->writeback = true; in writeback()
1308 mg->writeback = false; in demote_then_promote()
[all …]
DKconfig295 cleaned etc. It supports writeback and writethrough modes.
/linux-4.1.27/include/linux/
Dnfs_fs_sb.h133 atomic_long_t writeback; /* number of writeback pages */ member
Dpage-flags.h243 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.1.27/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.1.27/include/uapi/drm/
Dexynos_drm.h183 __u32 writeback; member
/linux-4.1.27/Documentation/devicetree/bindings/media/
Dsamsung-fimc.txt88 writeback input.
90 writeback input.
/linux-4.1.27/fs/
DMakefile12 seq_file.o xattr.o libfs.o fs-writeback.o \
Dbuffer.c84 bool *dirty, bool *writeback) in buffer_check_dirty_writeback() argument
88 *writeback = false; in buffer_check_dirty_writeback()
96 *writeback = true; in buffer_check_dirty_writeback()
102 *writeback = true; in buffer_check_dirty_writeback()
Dbinfmt_elf.c1605 if (regset->writeback) in do_thread_regset_writeback()
1606 regset->writeback(task, regset, 1); in do_thread_regset_writeback()
/linux-4.1.27/Documentation/vm/
Dpage_migration93 2. Insure that writeback is complete.
135 15. Queued up writeback on the new page is triggered.
/linux-4.1.27/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.1.27/fs/nfs/
Dfile.c510 bool *dirty, bool *writeback) in nfs_check_dirty_writeback() argument
525 *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()
1726 if (atomic_long_read(&nfss->writeback) < NFS_CONGESTION_OFF_THRESH) in nfs_commit_release_pages()
/linux-4.1.27/fs/proc/
Dtask_mmu.c1350 unsigned long writeback; member
1378 md->writeback += nr_pages; in gather_stats()
1557 if (md->writeback) in show_numa_map()
1558 seq_printf(m, " writeback=%lu", md->writeback); in show_numa_map()
/linux-4.1.27/arch/mn10300/kernel/
Dhead.S392 # flush the local cache if it's in writeback mode
/linux-4.1.27/drivers/staging/lustre/lustre/llite/
Dvvp_dev.c427 seq_page_flag(seq, vmpage, writeback, has_flags); in vvp_pgcache_page_show()
/linux-4.1.27/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.1.27/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.1.27/arch/x86/kvm/
Demulate.c1713 static int writeback(struct x86_emulate_ctxt *ctxt, struct operand *op) in writeback() function
4974 goto writeback; in x86_emulate_insn()
4979 goto writeback; in x86_emulate_insn()
5049 writeback: in x86_emulate_insn()
5052 rc = writeback(ctxt, &ctxt->src); in x86_emulate_insn()
5057 rc = writeback(ctxt, &ctxt->dst); in x86_emulate_insn()
5167 goto writeback; in x86_emulate_insn()
Dx86.c2717 int writeback) in msr_io() argument
2744 if (writeback && copy_to_user(user_msrs->entries, entries, size)) in msr_io()
5376 bool writeback = true; in x86_emulate_instruction() local
5461 writeback = false; in x86_emulate_instruction()
5467 writeback = false; in x86_emulate_instruction()
5475 if (writeback) { in x86_emulate_instruction()
/linux-4.1.27/arch/m68k/mac/
Dconfig.c140 static void mac_cache_card_flush(int writeback) in mac_cache_card_flush() argument
/linux-4.1.27/fs/btrfs/
Draid56.c2342 goto writeback; in finish_parity_scrub()
2406 writeback: in finish_parity_scrub()
/linux-4.1.27/fs/ceph/
Dcaps.c2496 bool writeback = false; in handle_cap_grant() local
2645 writeback = true; /* initiate writeback; will delay ack */ in handle_cap_grant()
2700 if (writeback) in handle_cap_grant()
/linux-4.1.27/drivers/gpu/drm/exynos/
Dexynos_drm_gsc.c1334 prop_list->writeback = 1; in gsc_init_prop_list()
Dexynos_drm_fimc.c1264 prop_list->writeback = 1; in fimc_init_prop_list()
/linux-4.1.27/arch/ia64/kernel/
Dptrace.c2110 .writeback = gpregs_writeback
/linux-4.1.27/Documentation/cgroups/
Dmemory.txt496 writeback - # of bytes of file/anon cache that are queued for syncing to
/linux-4.1.27/Documentation/trace/
Dftrace.txt2408 echo '!writeback*:mod:ext3' >> set_ftrace_filter
/linux-4.1.27/arch/x86/
DKconfig1570 add writeback entries.