Home
last modified time | relevance | path

Searched refs:flushing (Results 1 – 52 of 52) sorted by relevance

/linux-4.1.27/arch/mn10300/mm/
DKconfig.cache38 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.1.27/drivers/staging/speakup/
Dspeakup_soft.c219 if (!synth_buffer_empty() || speakup_info.flushing) in softsynth_read()
238 if (speakup_info.flushing) { in softsynth_read()
239 speakup_info.flushing = 0; in softsynth_read()
291 if (!synth_buffer_empty() || speakup_info.flushing) in softsynth_poll()
Dsynth.c41 .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()
Dthread.c34 (speakup_info.flushing || in speakup_thread()
Dspeakup_apollo.c161 if (speakup_info.flushing) { in do_catch_up()
162 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_decext.c176 if (speakup_info.flushing) { in do_catch_up()
177 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_keypc.c199 if (speakup_info.flushing) { in do_catch_up()
200 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_acntpc.c198 if (speakup_info.flushing) { in do_catch_up()
199 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_dectlk.c240 if (speakup_info.flushing) { in do_catch_up()
241 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_dtlk.c210 if (speakup_info.flushing) { in do_catch_up()
211 speakup_info.flushing = 0; in do_catch_up()
Dspeakup_decpc.c392 if (speakup_info.flushing) { in do_catch_up()
393 speakup_info.flushing = 0; in do_catch_up()
Dspk_types.h197 int flushing; member
/linux-4.1.27/Documentation/
Dcachetlb.txt6 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
Ddma-buf-sharing.txt267 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
D00-INDEX113 - describes the cache/TLB flushing interfaces Linux uses.
Dxillybus.txt303 Note that the issue of partial buffer flushing is irrelevant for pipes having
Dkernel-parameters.txt427 fullflush - enable flushing of IO/TLB entries when
558 firmware feature for flushing multiple hpte entries
3316 Set s390 IOTLB flushing mode
3318 With strict flushing every unmap operation will result in
3319 an IOTLB flush. Default is lazy flushing before reuse,
DDMA-API-HOWTO.txt319 explicit software flushing.
/linux-4.1.27/fs/ceph/
Dcaps.c1129 int op, int used, int want, int retain, int flushing, in __send_cap() argument
1193 if (flushing) { in __send_cap()
1206 if (flushing & (1 << i)) in __send_cap()
1229 if (flushing & CEPH_CAP_XATTR_EXCL) { in __send_cap()
1240 op, keep, want, flushing, seq, flush_tid, issue_seq, mseq, in __send_cap()
1452 int flushing; in __mark_caps_flushing() local
1457 flushing = ci->i_dirty_caps; in __mark_caps_flushing()
1459 ceph_cap_string(flushing), in __mark_caps_flushing()
1461 ceph_cap_string(ci->i_flushing_caps | flushing)); in __mark_caps_flushing()
1462 ci->i_flushing_caps |= flushing; in __mark_caps_flushing()
[all …]
/linux-4.1.27/include/trace/events/
Djbd2.h246 __field( unsigned long, flushing )
260 __entry->flushing = stats->rs_flushing;
275 jiffies_to_msecs(__entry->flushing),
/linux-4.1.27/drivers/infiniband/hw/mlx4/
Dmcg.c682 } else if (method == IB_SA_METHOD_DELETE_RESP && group->demux->flushing) in mlx4_ib_mcg_work_handler()
941 if (ctx->flushing) in mlx4_ib_mcg_multiplex_handler()
1054 ctx->flushing = 0; in mlx4_ib_mcg_port_init()
1122 cw->ctx->flushing = 0; in mcg_clean_task()
1130 if (ctx->flushing) in mlx4_ib_mcg_port_cleanup()
1133 ctx->flushing = 1; in mlx4_ib_mcg_port_cleanup()
1137 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup()
1143 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup()
Dmlx4_ib.h439 int flushing; /* flushing the work queue */ member
/linux-4.1.27/fs/xfs/
Dxfs_trans_ail.c339 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.1.27/arch/mips/sgi-ip27/
DTODO19 13. Cache flushing (specially the SMP version) has to be investigated.
/linux-4.1.27/Documentation/block/
Dwriteback_cache_control.txt45 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.1.27/drivers/vhost/
Dvhost.c66 work->flushing = 0; in vhost_work_init()
133 int flushing; in vhost_work_flush() local
137 work->flushing++; in vhost_work_flush()
141 flushing = --work->flushing; in vhost_work_flush()
143 BUG_ON(flushing < 0); in vhost_work_flush()
221 if (work->flushing) in vhost_worker()
Dvhost.h22 int flushing; member
/linux-4.1.27/fs/btrfs/
Ddelayed-ref.h156 int flushing; member
Dtransaction.c232 cur_trans->delayed_refs.flushing = 0; in join_transaction()
723 cur_trans->delayed_refs.flushing) in btrfs_should_end_transaction()
1807 cur_trans->delayed_refs.flushing = 1; in btrfs_commit_transaction()
Dextent-tree.c4669 bool flushing = false; in reserve_metadata_bytes() local
4678 while (flush == BTRFS_RESERVE_FLUSH_ALL && !flushing && in reserve_metadata_bytes()
4750 flushing = true; in reserve_metadata_bytes()
4806 if (flushing) { in reserve_metadata_bytes()
/linux-4.1.27/Documentation/device-mapper/
Dlog-writes.txt19 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.1.27/arch/arm/mm/
Dcache-v7.S96 bne start_flush_levels @ LoU != 0, start flushing
104 beq start_flush_levels @ start flushing cache levels
/linux-4.1.27/Documentation/virtual/kvm/
Dhypercalls.txt51 flushing TLB, release PT.
/linux-4.1.27/Documentation/x86/
Dtlb.txt14 address space is obviously better performed by flushing the
/linux-4.1.27/drivers/net/wireless/ath/ath6kl/
Dtxrx.c697 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.1.27/arch/cris/arch-v32/mm/
Dmmu.S72 ; The workaround detects such loops and exits them by flushing
/linux-4.1.27/drivers/firewire/
Dohci.c136 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.1.27/arch/sh/mm/
DKconfig262 unfortunately still require the majority of flushing functions to
/linux-4.1.27/Documentation/filesystems/
Dxfs-delayed-logging-design.txt165 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.1.27/Documentation/filesystems/pohmelfs/
Dnetwork_protocol.txt212 and is capable of flushing pages based on that, it is not used, since all Linux
/linux-4.1.27/Documentation/scsi/
Dst.txt93 write the filemarks without flushing the drive buffer. Writing filemark at
94 close() is always flushing the drive buffers. However, if the previous
DChangeLog.sym53c8xx257 bridge misbehaviour regarding posted write flushing.
/linux-4.1.27/scripts/
Dspelling.txt420 flusing||flushing
/linux-4.1.27/Documentation/powerpc/
Deeh-pci-error-recovery.txt309 unmount a file system without flushing pending buffers, but this
/linux-4.1.27/arch/blackfin/
DKconfig899 If enabled, the Blackfin icache flushing functions are linked
912 If enabled, the Blackfin dcache flushing functions are linked
/linux-4.1.27/Documentation/networking/
Dtimestamping.txt232 the situation by always flushing the TCP stack in between requests,
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Didle-states.txt64 like cache flushing. This is abortable on pending wake-up
/linux-4.1.27/crypto/
DKconfig170 algorithms for submitting jobs and flushing jobs in multi-buffer
/linux-4.1.27/Documentation/filesystems/cifs/
DREADME520 delaying slightly flushing the data to disk on the server),
/linux-4.1.27/drivers/scsi/aic7xxx/
Daic7xxx.seq946 * the flushing process now. We'll poke
/linux-4.1.27/arch/arm/
DKconfig1128 tables. The workaround changes the TLB flushing routines to invalidate
/linux-4.1.27/Documentation/RCU/
DRTFP.txt547 application to linked list update and log-buffer flushing.