| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | thread_safety_dpdk_functions.rst | 15 Mechanisms such as atomics or locking can be used that will allow execution blocks to operate seria…
30 cannot be done in multiple threads without using locking when a single hash or LPM table is accesse…
31 Another alternative to locking would be to create multiple instances of these tables allowing each …
34 and it is recommended that no locking be used as it will impact performance.
38 then locking, or some other form of mutual exclusion, is necessary.
75 it is up to the application to provide the appropriate locking or mutual exclusion restrictions aro…
|
| H A D | writing_efficient_code.rst | 182 Also, some locking techniques are more efficient than others.
|
| H A D | rcu_lib.rst | 10 They enable use cases where locking may not be allowed
|
| H A D | hash_lib.rst | 96 … operations will be slower because of the overhead associated with the software locking mechanisms.
|
| H A D | compressdev.rst | 608 application onus to use proper locking mechanism to ensure exclusive enqueuing
|
| H A D | qos_framework.rst | 369 …which requires either using locking primitives for access serialization (for example, spinlocks/ s…
|
| /f-stack/freebsd/kern/ |
| H A D | vnode_if.src | 35 # is a specification of the locking protocol used by each vop call.
39 # return, and the "error" column defines the locking state on error exit.
41 # The locking value can take the following values:
66 # XXX - the lookup locking protocol defies simple description and depends
|
| /f-stack/tools/route/ |
| H A D | route.c | 122 static int locking, lockrest, debugonly; variable
850 if (lockrest || locking) in set_metric()
852 if (locking) in set_metric()
853 locking = 0; in set_metric()
935 locking = 1; in newroute()
|
| /f-stack/app/redis-5.0.5/deps/jemalloc/include/jemalloc/internal/ |
| H A D | jemalloc_internal_defs.h.in | 183 /* Support lazy locking (avoid locking unless a second thread is launched). */
|
| /f-stack/freebsd/contrib/device-tree/Bindings/mtd/ |
| H A D | mtd-physmap.txt | 31 Bits) locking.
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | run_app.rst | 455 Enable locking all memory.
459 Disable locking all memory.
|
| /f-stack/dpdk/doc/guides/faq/ |
| H A D | faq.rst | 147 Currently the table implementation is not a thread safe implementation and assumes that locking bet…
|
| /f-stack/freebsd/i386/conf/ |
| H A D | NOTES | 107 # CPU_CYRIX_NO_LOCK enables weak locking for the entire address space
170 # Pentiums) from locking up when a LOCK CMPXCHG8B instruction is
|
| /f-stack/app/redis-5.0.5/deps/jemalloc/ |
| H A D | ChangeLog | 133 locking and/or background threads). This mitigates an initialization
972 - Fix a locking order bug that could cause deadlock during fork if heap
1089 - Disable lazy locking by default.
1243 - Avoid locking in mallctl*() when possible.
|
| H A D | INSTALL.md | 185 mutex locking/unlocking operations while in single-threaded mode. In
|
| H A D | configure.ac | 1687 dnl Disable lazy locking by default.
1690 [Enable lazy locking (only lock when multi-threaded)])],
|
| H A D | configure | 1441 --enable-lazy-lock Enable lazy locking (only lock when multi-threaded)
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | mvpp2.rst | 52 need to be allocated, locking will have to be considered. Number of available
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | performance_thread.rst | 483 data structures, lock free constructs or else explicit locking will be
691 Recursive locking is not supported with L-threads, attempts to take a lock
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_17_11.rst | 319 atomic locking of the services has been fixed and refactored for readability.
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | coding_style.rst | 284 …ata-path code, when there are several consumer and/or producers to avoid locking for concurrent ac…
|
| /f-stack/freebsd/contrib/dev/acpica/ |
| H A D | changes.txt | 3804 GPE by removing GPE register locking. As such, raw handlers much provide
9126 unloads. Added a reader/writer locking mechanism to allow multiple
9216 Optimized the ACPI register locking. Removed locking for reads from the
9986 Simplified the internal ACPI hardware interfaces to eliminate the locking
11383 Fixed two issues with the locking of the internal namespace data
11503 Converted the locking mutex used for the ACPI hardware to a spinlock.
|