Home
last modified time | relevance | path

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

12

/linux/Documentation/translations/ko_KR/
H A Dmemory-barriers.txt504 ACQUIRE 오퍼레이션은 거의 항상 RELEASE 오퍼레이션과 짝을 지어 사용되어야
508 (6) RELEASE 오퍼레이션.
510 이 타입의 오퍼레이션들도 단방향 투과성 배리어처럼 동작합니다. RELEASE
511 오퍼레이션 앞의 모든 메모리 오퍼레이션들은 RELEASE 오퍼레이션 전에 완료된
513 오퍼레이션들과 smp_store_release() 오퍼레이션도 RELEASE 오퍼레이션의
516 RELEASE 오퍼레이션 뒤의 메모리 오퍼레이션들은 RELEASE 오퍼레이션이
519 ACQUIRE 와 RELEASE 오퍼레이션의 사용은 일반적으로 다른 메모리 배리어의
520 필요성을 없앱니다. 또한, RELEASE+ACQUIRE 조합은 범용 메모리 배리어처럼
521 동작할 것을 보장하지 -않습니다-. 하지만, 어떤 변수에 대한 RELEASE
522 오퍼레이션을 앞서는 메모리 액세스들의 수행 결과는 이 RELEASE 오퍼레이션을
[all …]
/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/Documentation/core-api/
H A Drefcount-vs-atomic.rst49 A RELEASE memory ordering guarantees that all prior loads and
110 * fully unordered --> RELEASE ordering
139 * fully ordered --> RELEASE ordering + ACQUIRE ordering on success
152 * fully ordered --> RELEASE ordering + control dependency
167 * fully ordered --> RELEASE ordering + control dependency + hold
/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 Dnv84_fence.c50 NVDEF(NV826F, SEMAPHORED, OPERATION, RELEASE), in nv84_fence_emit32()
/linux/drivers/s390/char/
H A Dtape_std.h56 #define RELEASE 0xD4 /* 3420 NOP, 3480 REJECT */ macro
/linux/drivers/usb/storage/
H A Ddebug.c62 case RELEASE: what = "RELEASE"; break; in usb_stor_show_command()
/linux/include/scsi/
H A Dscsi_proto.h37 #define RELEASE 0x17 macro
/linux/drivers/target/
H A Dtarget_core_spc.c1679 case RELEASE: in tcm_is_pr_enabled()
1831 .opcode = RELEASE,
1833 .usage_bits = {RELEASE, 0x00, 0x00, 0x00,
2272 case RELEASE: in spc_parse_cdb()
2316 case RELEASE: in spc_parse_cdb()
H A Dtarget_core_device.c1081 (cdb[0] == RELEASE || cdb[0] == RELEASE_10) || in passthrough_parse_cdb()
1104 if (cdb[0] == RELEASE || cdb[0] == RELEASE_10) { in passthrough_parse_cdb()
H A Dtarget_core_pr.c94 case RELEASE: in target_scsi2_reservation_check()
421 case RELEASE: in core_scsi3_pr_seq_non_holder()
/linux/include/trace/events/
H A Dtarget.h35 scsi_opcode_name(RELEASE), \
H A Dscsi.h33 scsi_opcode_name(RELEASE), \
/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 DMakefile30 RELEASE ?= macro
31 OPT_FLAGS ?= $(if $(RELEASE),-O2,-O0)
/linux/drivers/scsi/megaraid/
H A Dmegaraid_mbox.c1729 case RELEASE: in DEF_SCSI_QCMD()
2338 scp->cmnd[0] == RELEASE)) { in megaraid_mbox_dpc()
/linux/Documentation/driver-api/soundwire/
H A Dstream.rst495 Bus implements below APIs for RELEASE state which needs to be called by

12