Home
last modified time | relevance | path

Searched refs:locking (Results 1 – 25 of 114) sorted by relevance

12345

/src/contrib/ntp/sntp/libevent/
H A Dbufferevent-internal.h486 struct bufferevent_private *locking = BEV_UPCAST(b); \
487 EVLOCK_LOCK(locking->lock, 0); \
492 struct bufferevent_private *locking = BEV_UPCAST(b); \
493 EVLOCK_UNLOCK(locking->lock, 0); \
/src/contrib/libevent/
H A Dbufferevent-internal.h486 struct bufferevent_private *locking = BEV_UPCAST(b); \
487 EVLOCK_LOCK(locking->lock, 0); \
492 struct bufferevent_private *locking = BEV_UPCAST(b); \
493 EVLOCK_UNLOCK(locking->lock, 0); \
/src/contrib/unbound/libunbound/
H A Dcontext.c198 context_obtain_alloc(struct ub_ctx* ctx, int locking) in context_obtain_alloc() argument
202 if(locking) { in context_obtain_alloc()
209 if(locking) { in context_obtain_alloc()
225 int locking) in context_release_alloc() argument
229 if(locking) { in context_release_alloc()
234 if(locking) { in context_release_alloc()
H A Dcontext.h241 struct alloc_cache* context_obtain_alloc(struct ub_ctx* ctx, int locking);
250 int locking);
/src/crypto/openssl/doc/designs/quic-design/
H A Dquic-thread-assist.md11 At first glance, one could synchronise handshake layer public APIs by locking a
15 the locking to every single public HL-related API call.
25 For locking of API calls the lock would only be held for the separate get and
31 - **1. Application-controlled explicit locking.**
H A Dquic-concurrency.md43 Model, calls to SSL objects are not synchronised. There is no locking on any
88 contention, there is an emphasis on message passing over locking.
147 Since UCM is basically a slight optimisation of CCM in which unnecessary locking
251 locking (if any) internally.
/src/sys/contrib/openzfs/config/
H A Dkernel-filelock.m44 dnl # locking support functions (eg generic_setlease) were moved out of
/src/contrib/sendmail/
H A DKNOWNBUGS23 * Berkeley DB map locking problem with fcntl().
25 For Linux the default is to use fcntl() for file locking. However,
234 * Berkeley DB 2.X race condition with fcntl() locking
237 operating systems which use fcntl() style locking, such as
241 reopens it. fcntl() locking drops the lock when any file
267 permission failure race as sendmail checks the permissions before locking
H A DREADME117 Any application which uses either flock() or fcntl() style locking or
118 other APIs that use one of these locking methods (such as open() with
122 File locking is used throughout sendmail for a variety of files
127 statistics files. For system which use flock() for file locking, a
155 use fcntl() style locking. Since it does not interfere with normal
329 File locking using fcntl() does not interoperate with Berkeley DB
427 it does mailbox locking differently than other systems.
/src/contrib/sendmail/libsmutil/
H A Dt-maplock-0.sh36 $0: test basic makemap locking;
/src/contrib/llvm-project/libcxx/modules/std/
H A Dmutex.inc36 // [thread.lock.algorithm], generic locking algorithms
/src/crypto/openssl/doc/man3/
H A DX509_STORE_new.pod7 - X509_STORE allocation, freeing and locking functions
H A DBN_CTX_new.pod45 locking is performed, and the internal pool allocator will not properly handle
/src/crypto/openssl/doc/man7/
H A DEVP_RAND.pod104 by its child DRBG instances. The necessary locking is done internally.
109 locking via the EVP_RAND interface.
117 All other DRBG instances created by an application don't support locking,
135 RAND_add() ==> <primary> <-| shared DRBG (with locking) |
H A Dopenssl-threads.pod75 will do any necessary locking.
76 Some API's, such as L<NCONF_load(3)> and related do no locking at all;
H A Dprovider-rand.pod139 When DRBGs are used by multiple threads, there must be locking employed to
140 ensure their proper operation. Because locking introduces an overhead, it
143 OSSL_FUNC_rand_enable_locking() allows locking to be turned on for a DRBG and all of
H A Dopenssl-quic-concurrency.pod80 The B<Single-Threaded Concurrency Model (SCM)> performs no locking or
89 The B<Contentive Concurrency Model (CCM)> performs automatic locking when making
95 This concurrency model adds the overhead of locking over the Single-Threaded
/src/usr.sbin/cron/doc/
H A DTHANKS13 Paul Close made a suggestion which led to /etc/crond.pid and the mutex locking
/src/crypto/openssl/include/openssl/
H A Dcrypto.h.in276 * The old locking functions have been removed completely without compatibility
279 * Replacing the locking functions with no-ops would cause race condition
282 * On the other hand, the locking callbacks are no longer used. Consequently,
292 * These defines where used in combination with the old locking callbacks,
/src/crypto/krb5/src/plugins/kdb/db2/libdb2/include/
H A Ddb.hin99 #define DB_LOCK 0x20000000 /* Do locking. */
103 #define DB_LOCK 0x2000 /* Do locking. */
/src/sys/kern/
H A Dvnode_if.src31 # is a specification of the locking protocol used by each vop call.
35 # return, and the "error" column defines the locking state on error exit.
37 # The locking value can take the following values:
62 # XXX - the lookup locking protocol defies simple description and depends
/src/sys/geom/
H A Dnotes16 therefore the two fields do not generally need locking. These
61 the bio when it is completed. There are no concurrency or locking
/src/sbin/route/
H A Droute.c91 static int locking, lockrest; variable
815 if (lockrest || locking) in set_metric()
817 if (locking) in set_metric()
818 locking = 0; in set_metric()
900 locking = 1; in newroute()
/src/contrib/sendmail/contrib/
H A Dmailprio94 $locking = "flock"; # "flock" or "fcntl"
255 # File locking
283 X if ($locking eq "flock") {
361 X In mailprio check: #!perl path, $home, $priodb, $locking
/src/lib/libc/locale/
H A DDESIGN.xlocale38 and it can therefore be used without locking. It is the responsibility of the
104 calls to `localeconv()`. This is not protected by any locking, however this is

12345