Home
last modified time | relevance | path

Searched refs:RELEASE (Results 1 – 20 of 20) sorted by relevance

/linux/Documentation/translations/zh_CN/core-api/
H A Drefcount-vs-atomic.rst47 RELEASE内存顺序保证了在同一CPU上所有较早加载和存储的指令（所有程序顺序较早
100 * 完全无序的 --> RELEASE顺序
128 * 完全有序的 --> RELEASE顺序 + 成功后ACQUIRE顺序
141 * 完全有序的 --> RELEASE顺序 + 控制依赖
156 * 完全有序 --> RELEASE顺序 + 控制依赖 + 持有
/linux/tools/testing/selftests/drivers/net/
H A Dnetcons_sysdata.sh
/linux/Documentation/trace/rv/
H A Dlinear_temporal_logic.rst95 RULE = always (ACQUIRE imply ((not KILLED and not CRASHED) until RELEASE))
97 which says: if `ACQUIRE`, then `RELEASE` must happen before `KILLED` or
104 RULE = always (ACQUIRE imply (ALIVE until RELEASE))
/linux/Documentation/
H A Dmemory-barriers.txt485 An ACQUIRE operation should almost always be paired with a RELEASE
489 (6) RELEASE operations.
492 memory operations before the RELEASE operation will appear to happen
493 before the RELEASE operation with respect to the other components of the
494 system. RELEASE operations include UNLOCK operations and
497 Memory operations that occur after a RELEASE operation may appear to
500 The use of ACQUIRE and RELEASE operations generally precludes the need
501 for other sorts of memory barrier. In addition, a RELEASE+ACQUIRE pair is
504 RELEASE on that same variable are guaranteed to be visible. In other
510 RELEASE acts as a minimal "release" operation.
[all …]
H A Datomic_bitops.txt64 clear_bit_unlock() which has RELEASE semantics and test_bit_acquire which has
H A Datomic_t.txt178 {}_release: the W of the RMW (or atomic_set) is a RELEASE
225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than
226 a RELEASE because it orders preceding instructions against both the read
/linux/Documentation/translations/sp_SP/
H A Dmemory-barriers.txt516 operación RELEASE (de liberación).
519 (6) Operaciones RELEASE (de liberación).
523 RELEASE parecerán ocurrir antes de la operación RELEASE con respecto a
524 los demás componentes del sistema. Las operaciones de RELEASE incluyen
528 RELEASE pueden parecer suceder antes de que se complete.
530 El uso de las operaciones ACQUIRE y RELEASE generalmente excluye la
532 RELEASE+ACQUIRE NO garantiza actuar como una barrera de memoria
535 RELEASE en esa misma variable están garantizados como visibles. En
541 "adquisición" y RELEASE actúa como una operación mínima de
545 contiene variantes de ACQUIRE y RELEASE, además de definiciones
[all …]
/linux/Documentation/translations/zh_CN/locking/
H A Dspinlocks.rst37 (6) RELEASE operations.
/linux/drivers/gpu/drm/nouveau/
H A Dnvc0_fence.c47 NVDEF(NV906F, SEMAPHORED, OPERATION, RELEASE) | in nvc0_fence_emit32()
H A Dgv100_fence.c30 NVDEF(NVC36F, SEM_EXECUTE, OPERATION, RELEASE) | in gv100_fence_emit32()
H A Dnv84_fence.c50 NVDEF(NV826F, SEMAPHORED, OPERATION, RELEASE), in nv84_fence_emit32()
/linux/arch/m68k/ifpsp060/
H A DMISC29 RELEASE FILE VERSIONS:
H A DCHANGES30 CHANGES SINCE LAST RELEASE:
/linux/Documentation/locking/
H A Dspinlocks.rst30 (6) RELEASE operations.
/linux/drivers/usb/image/
H A Dmicrotek.c247 case RELEASE: what = "RELEASE"; break; in mts_show_command()
/linux/tools/testing/selftests/bpf/
H A DMakefile36 RELEASE ?= macro
37 OPT_FLAGS ?= $(if $(RELEASE),-O2,-O0)
/linux/Documentation/networking/device_drivers/ethernet/cirrus/
H A Dcs89x0.rst375 Refer to the RELEASE.TXT file distributed as part of this archive for a list of
/linux/Documentation/scsi/
H A DBusLogic.rst11 PRODUCTION RELEASE
H A DChangeLog.lpfc2 * Please read the associated RELEASE-NOTES file !!!
/linux/net/core/
H A Ddev.c1868 N(POST_INIT) N(PRE_UNINIT) N(RELEASE) N(NOTIFY_PEERS) N(JOIN) in netdev_cmd_to_name()