/linux-4.4.14/arch/mn10300/mm/ |
D | Kconfig.cache | 38 This is not available for use with an SMP kernel if cache flushing 58 This determines the method by which CPU cache flushing and 95 Set if we need the dcache flushing before the icache is invalidated. 101 write-through mode and doesn't need flushing. 104 # The kernel debugger gets its own separate cache flushing functions
|
/linux-4.4.14/drivers/staging/speakup/ |
D | speakup_soft.c | 220 if (!synth_buffer_empty() || speakup_info.flushing) in softsynth_read() 239 if (speakup_info.flushing) { in softsynth_read() 240 speakup_info.flushing = 0; in softsynth_read() 292 if (!synth_buffer_empty() || speakup_info.flushing) in softsynth_poll()
|
D | synth.c | 41 .flushing = 0, 105 if (speakup_info.flushing) { in spk_do_catch_up() 106 speakup_info.flushing = 0; in spk_do_catch_up() 219 speakup_info.flushing = 1; in spk_do_flush()
|
D | thread.c | 34 (speakup_info.flushing || in speakup_thread()
|
D | speakup_apollo.c | 161 if (speakup_info.flushing) { in do_catch_up() 162 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_decext.c | 176 if (speakup_info.flushing) { in do_catch_up() 177 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_acntpc.c | 198 if (speakup_info.flushing) { in do_catch_up() 199 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_keypc.c | 199 if (speakup_info.flushing) { in do_catch_up() 200 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_dectlk.c | 240 if (speakup_info.flushing) { in do_catch_up() 241 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_dtlk.c | 210 if (speakup_info.flushing) { in do_catch_up() 211 speakup_info.flushing = 0; in do_catch_up()
|
D | speakup_decpc.c | 393 if (speakup_info.flushing) { in do_catch_up() 394 speakup_info.flushing = 0; in do_catch_up()
|
D | spk_types.h | 197 int flushing; member
|
/linux-4.4.14/drivers/staging/android/ |
D | TODO | 13 - Remove ION_IOC_CUSTOM: Atm used for cache flushing for cpu access in some 20 need flushing.
|
/linux-4.4.14/Documentation/ |
D | cachetlb.txt | 6 This document describes the cache/tlb flushing interfaces called 16 thinking SMP cache/tlb flushing must be so inefficient, this is in 22 First, the TLB flushing interfaces, since they are the simplest. The 55 Here we are flushing a specific range of (user) virtual 113 Next, we have the cache flushing interfaces. In general, when Linux 135 The cache flushing routines below need only deal with cache flushing 170 Here we are flushing a specific range of (user) virtual 220 Here in these two interfaces we are flushing a specific range 341 Any necessary cache flushing or other coherency operations 387 coherency. It must do this by flushing the vmap range before doing
|
D | dma-buf-sharing.txt | 267 direction can be used by the exporter to optimize the cache flushing, i.e. 326 it needs to announce this to the exporter (to facilitate cache flushing and 392 leaving the cpu domain and flushing caches at fault time. Note that all the
|
D | 00-INDEX | 113 - describes the cache/TLB flushing interfaces Linux uses.
|
D | xillybus.txt | 303 Note that the issue of partial buffer flushing is irrelevant for pipes having
|
D | kernel-parameters.txt | 434 fullflush - enable flushing of IO/TLB entries when 565 firmware feature for flushing multiple hpte entries 3436 Set s390 IOTLB flushing mode 3438 With strict flushing every unmap operation will result in 3439 an IOTLB flush. Default is lazy flushing before reuse,
|
D | DMA-API-HOWTO.txt | 319 explicit software flushing.
|
/linux-4.4.14/include/trace/events/ |
D | jbd2.h | 246 __field( unsigned long, flushing ) 260 __entry->flushing = stats->rs_flushing; 275 jiffies_to_msecs(__entry->flushing),
|
/linux-4.4.14/drivers/infiniband/hw/mlx4/ |
D | mcg.c | 686 } else if (method == IB_SA_METHOD_DELETE_RESP && group->demux->flushing) in mlx4_ib_mcg_work_handler() 945 if (ctx->flushing) in mlx4_ib_mcg_multiplex_handler() 1058 ctx->flushing = 0; in mlx4_ib_mcg_port_init() 1126 cw->ctx->flushing = 0; in mcg_clean_task() 1134 if (ctx->flushing) in mlx4_ib_mcg_port_cleanup() 1137 ctx->flushing = 1; in mlx4_ib_mcg_port_cleanup() 1141 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup() 1147 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup()
|
D | mlx4_ib.h | 454 int flushing; /* flushing the work queue */ member
|
/linux-4.4.14/fs/ceph/ |
D | caps.c | 1109 int op, int used, int want, int retain, int flushing, in __send_cap() argument 1171 follows = flushing ? ci->i_head_snapc->seq : 0; in __send_cap() 1188 if (flushing & CEPH_CAP_XATTR_EXCL) { in __send_cap() 1199 op, keep, want, flushing, seq, in __send_cap() 1492 int flushing; in __mark_caps_flushing() local 1498 flushing = ci->i_dirty_caps; in __mark_caps_flushing() 1500 ceph_cap_string(flushing), in __mark_caps_flushing() 1502 ceph_cap_string(ci->i_flushing_caps | flushing)); in __mark_caps_flushing() 1503 ci->i_flushing_caps |= flushing; in __mark_caps_flushing() 1508 cf->caps = flushing; in __mark_caps_flushing() [all …]
|
/linux-4.4.14/fs/xfs/ |
D | xfs_trans_ail.c | 339 int flushing = 0; in xfsaild_push() local 409 flushing++; in xfsaild_push() 469 } else if (((stuck + flushing) * 100) / count > 90) { in xfsaild_push()
|
/linux-4.4.14/arch/mips/sgi-ip27/ |
D | TODO | 19 13. Cache flushing (specially the SMP version) has to be investigated.
|
/linux-4.4.14/Documentation/block/ |
D | writeback_cache_control.txt | 45 worry if the underlying devices need any explicit cache flushing and how 71 driver needs to tell the block layer that it supports flushing caches by
|
/linux-4.4.14/drivers/vhost/ |
D | vhost.c | 143 work->flushing = 0; in vhost_work_init() 210 int flushing; in vhost_work_flush() local 214 work->flushing++; in vhost_work_flush() 218 flushing = --work->flushing; in vhost_work_flush() 220 BUG_ON(flushing < 0); in vhost_work_flush() 300 if (work->flushing) in vhost_worker()
|
D | vhost.h | 22 int flushing; member
|
/linux-4.4.14/fs/btrfs/ |
D | delayed-ref.h | 185 int flushing; member
|
D | transaction.c | 777 cur_trans->delayed_refs.flushing) in btrfs_should_end_transaction() 1842 cur_trans->delayed_refs.flushing = 1; in btrfs_commit_transaction()
|
D | extent-tree.c | 4881 bool flushing = false; in reserve_metadata_bytes() local 4890 while (flush == BTRFS_RESERVE_FLUSH_ALL && !flushing && in reserve_metadata_bytes() 4962 flushing = true; in reserve_metadata_bytes() 5018 if (flushing) { in reserve_metadata_bytes()
|
/linux-4.4.14/Documentation/device-mapper/ |
D | log-writes.txt | 19 make it easier to detect improper waiting/flushing. 38 Any REQ_FUA requests bypass this flushing mechanism and are logged as soon as
|
/linux-4.4.14/arch/arm/mm/ |
D | cache-v7.S | 96 bne start_flush_levels @ LoU != 0, start flushing 104 beq start_flush_levels @ start flushing cache levels
|
/linux-4.4.14/Documentation/virtual/kvm/ |
D | hypercalls.txt | 51 flushing TLB, release PT.
|
/linux-4.4.14/Documentation/x86/ |
D | tlb.txt | 14 address space is obviously better performed by flushing the
|
/linux-4.4.14/drivers/net/wireless/ath/ath6kl/ |
D | txrx.c | 697 bool flushing[ATH6KL_VIF_MAX] = {false}; in ath6kl_tx_complete() local 768 flushing[if_idx] = true; in ath6kl_tx_complete() 785 flushing[if_idx] = false; in ath6kl_tx_complete() 806 !flushing[vif->fw_vif_idx]) { in ath6kl_tx_complete()
|
/linux-4.4.14/arch/cris/arch-v32/mm/ |
D | mmu.S | 72 ; The workaround detects such loops and exits them by flushing
|
/linux-4.4.14/drivers/firewire/ |
D | ohci.c | 136 bool flushing; member 1431 ctx->flushing = true; in at_context_flush() 1433 ctx->flushing = false; in at_context_flush() 1447 if (last->transfer_status == 0 && !context->flushing) in handle_at_packet() 1481 if (context->flushing) in handle_at_packet() 1503 if (context->flushing) { in handle_at_packet()
|
/linux-4.4.14/arch/sh/mm/ |
D | Kconfig | 262 unfortunately still require the majority of flushing functions to
|
/linux-4.4.14/Documentation/filesystems/ |
D | xfs-delayed-logging-design.txt | 165 concurrent modification. Hence flushing the logical changes to the log would 171 flushing thread has the delayed logging tracking lock already held, and is 619 1. Locking out new transaction commits while flushing the CIL 623 Looking at the transaction commit and CIL flushing interactions, it is clear 641 flushing the CIL could involve walking a list of tens of thousands of log 647 It should also be noted that CIL flushing is also a relatively rare operation
|
/linux-4.4.14/Documentation/filesystems/pohmelfs/ |
D | network_protocol.txt | 212 and is capable of flushing pages based on that, it is not used, since all Linux
|
/linux-4.4.14/Documentation/scsi/ |
D | st.txt | 93 write the filemarks without flushing the drive buffer. Writing filemark at 94 close() is always flushing the drive buffers. However, if the previous
|
D | ChangeLog.sym53c8xx | 257 bridge misbehaviour regarding posted write flushing.
|
/linux-4.4.14/Documentation/powerpc/ |
D | eeh-pci-error-recovery.txt | 309 unmount a file system without flushing pending buffers, but this
|
/linux-4.4.14/scripts/ |
D | spelling.txt | 435 flusing||flushing
|
/linux-4.4.14/arch/blackfin/ |
D | Kconfig | 899 If enabled, the Blackfin icache flushing functions are linked 912 If enabled, the Blackfin dcache flushing functions are linked
|
/linux-4.4.14/Documentation/devicetree/bindings/arm/ |
D | idle-states.txt | 64 like cache flushing. This is abortable on pending wake-up
|
/linux-4.4.14/Documentation/networking/ |
D | timestamping.txt | 232 the situation by always flushing the TCP stack in between requests,
|
/linux-4.4.14/drivers/staging/lustre/ |
D | sysfs-fs-lustre | 598 performance, flushing write cache takes longer and as such
|
/linux-4.4.14/crypto/ |
D | Kconfig | 198 algorithms for submitting jobs and flushing jobs in multi-buffer
|
/linux-4.4.14/Documentation/filesystems/cifs/ |
D | README | 520 delaying slightly flushing the data to disk on the server),
|
/linux-4.4.14/drivers/scsi/aic7xxx/ |
D | aic7xxx.seq | 946 * the flushing process now. We'll poke
|
/linux-4.4.14/arch/arm/ |
D | Kconfig | 1141 tables. The workaround changes the TLB flushing routines to invalidate
|
/linux-4.4.14/Documentation/RCU/ |
D | RTFP.txt | 547 application to linked list update and log-buffer flushing.
|