Home
last modified time | relevance | path

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

12

/freebsd-14.2/sys/dev/mlx4/mlx4_ib/
H A Dmlx4_ib_mcg.c687 } 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()
1059 ctx->flushing = 0; in mlx4_ib_mcg_port_init()
1127 cw->ctx->flushing = 0; in mcg_clean_task()
1135 if (ctx->flushing) in mlx4_ib_mcg_port_cleanup()
1138 ctx->flushing = 1; in mlx4_ib_mcg_port_cleanup()
1142 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup()
1148 ctx->flushing = 0; in mlx4_ib_mcg_port_cleanup()
H A Dmlx4_ib.h461 int flushing; /* flushing the work queue */ member
/freebsd-14.2/tools/regression/nfsmmap/
H A DREADME9 Fsync, flushing the dirty range
/freebsd-14.2/contrib/llvm-project/compiler-rt/lib/xray/
H A Dxray_fdr_flags.inc22 "actually flushing the log; this gives a chance for threads to "
/freebsd-14.2/lib/libc/db/hash/
H A DREADME57 If you are using the ndbm interface and exit without flushing or closing the
/freebsd-14.2/contrib/ntp/sntp/m4/
H A Dntp_cacheversion.m460 # flushing would be counterproductive.
/freebsd-14.2/contrib/bc/
H A DMEMORY_BUGS.md27 possible out-of-bounds read when there is an error flushing `stdout` on exit
H A DNEWS.md35 The bug was that `bc` attempted to jump out when flushing `stdout` on exit, but
499 This is a production release that only adds one thing: flushing output when it
/freebsd-14.2/sys/contrib/openzfs/config/
H A Dkernel-make-request-fn.m4127 dnl # used to set flushing options
/freebsd-14.2/crypto/openssl/doc/man3/
H A DSSL_set_bio.pod39 If flushing is unnecessary with B<wbio>, L<BIO_flush(3)> should return one and
H A DSSL_CTX_set_session_cache_mode.pod77 flushing may be disabled and
H A DBIO_s_bio.pod117 transport before flushing the write buffer it will never succeed because the
/freebsd-14.2/contrib/llvm-project/llvm/lib/Support/Unix/
H A DMemory.inc184 // Therefore we need to temporarily add PROT_READ for the sake of flushing the
/freebsd-14.2/contrib/libxo/doc/
H A Doptions.rst101 F Force line-buffered flushing
/freebsd-14.2/sys/amd64/conf/
H A DFIRECRACKER164 # no need to worry about disks flushing caches before losing power.
/freebsd-14.2/contrib/llvm-project/llvm/lib/Support/Windows/
H A DPath.inc980 // As the flushing is quite expensive, use a heuristic to limit the
981 // cases where we do the flushing. Only do the flushing if we aren't
/freebsd-14.2/sys/i386/conf/
H A DNOTES104 # CPU_LOOP_EN prevents flushing the prefetch buffer if the destination
/freebsd-14.2/contrib/gdtoa/
H A DREADME119 arithmetic departs from the IEEE standard by flushing denormalized
/freebsd-14.2/sys/contrib/device-tree/Bindings/arm/
H A Didle-states.yaml72 like cache flushing. This is abortable on pending wake-up
/freebsd-14.2/sys/contrib/device-tree/Bindings/cpu/
H A Didle-states.yaml92 like cache flushing. This is abortable on pending wake-up
/freebsd-14.2/contrib/llvm-project/libcxx/include/
H A Dostream1110 // This is the path for the native API, start with flushing.
/freebsd-14.2/contrib/jemalloc/
H A DChangeLog844 "tcache.destroy" mallctls control tcache lifetime and flushing, and the
1474 - Fix crash in tcache flushing code during thread destruction.
/freebsd-14.2/contrib/file/
H A DChangeLog112 * detect filesystem full by flushing output (Dirk Mueller)
/freebsd-14.2/sys/dev/aic7xxx/
H A Daic7xxx.seq948 * the flushing process now. We'll poke
/freebsd-14.2/contrib/xz/
H A DChangeLog9250 5. Two seconds have passed and flushing starts.
9253 there was no pending data. This can cause flushing to occur more
9265 6. Two seconds have passed and flushing starts.
9306 millisecond and initiate flushing which would have nothing to

12