Searched refs:RELEASE (Results 1 – 25 of 30) sorted by relevance
12
502 ACQUIRE 오퍼레이션은 거의 항상 RELEASE 오퍼레이션과 짝을 지어 사용되어야506 (6) RELEASE 오퍼레이션.508 이 타입의 오퍼레이션들도 단방향 투과성 배리어처럼 동작합니다. RELEASE509 오퍼레이션 앞의 모든 메모리 오퍼레이션들은 RELEASE 오퍼레이션 전에 완료된511 오퍼레이션들과 smp_store_release() 오퍼레이션도 RELEASE 오퍼레이션의514 RELEASE 오퍼레이션 뒤의 메모리 오퍼레이션들은 RELEASE 오퍼레이션이517 ACQUIRE 와 RELEASE 오퍼레이션의 사용은 일반적으로 다른 메모리 배리어의519 알아두세요). 또한, RELEASE+ACQUIRE 조합은 범용 메모리 배리어처럼 동작할520 것을 보장하지 -않습니다-. 하지만, 어떤 변수에 대한 RELEASE 오퍼레이션을521 앞서는 메모리 액세스들의 수행 결과는 이 RELEASE 오퍼레이션을 뒤이어 같은[all …]
49 A RELEASE memory ordering guarantees that all prior loads and110 * fully unordered --> RELEASE ordering139 * fully ordered --> RELEASE ordering + ACQUIRE ordering on success152 * fully ordered --> RELEASE ordering + control dependency167 * fully ordered --> RELEASE ordering + control dependency + hold
479 An ACQUIRE operation should almost always be paired with a RELEASE483 (6) RELEASE operations.486 memory operations before the RELEASE operation will appear to happen487 before the RELEASE operation with respect to the other components of the488 system. RELEASE operations include UNLOCK operations and491 Memory operations that occur after a RELEASE operation may appear to494 The use of ACQUIRE and RELEASE operations generally precludes the need496 the subsection "MMIO write barrier"). In addition, a RELEASE+ACQUIRE499 RELEASE on that same variable are guaranteed to be visible. In other505 RELEASE acts as a minimal "release" operation.[all …]
178 {}_release: the W of the RMW (or atomic_set) is a RELEASE225 is a 'typical' RELEASE pattern, the barrier is strictly stronger than226 a RELEASE because it orders preceding instructions against both the read
67 clear_bit_unlock() which has RELEASE semantics.
56 #define RELEASE 0xD4 /* 3420 NOP, 3480 REJECT */ macro
63 case RELEASE: what = "RELEASE"; break; in usb_stor_show_command()
36 #define RELEASE 0x17 macro
35 scsi_opcode_name(RELEASE), \
33 scsi_opcode_name(RELEASE), \
29 RELEASE FILE VERSIONS:
30 CHANGES SINCE LAST RELEASE:
32 #define RELEASE 0x17 macro
1093 (cdb[0] == RELEASE || cdb[0] == RELEASE_10) || in passthrough_parse_cdb()1116 if (cdb[0] == RELEASE || cdb[0] == RELEASE_10) { in passthrough_parse_cdb()
1284 (cdb[0] == RELEASE || cdb[0] == RELEASE_10) || in spc_parse_cdb()1318 case RELEASE: in spc_parse_cdb()
94 case RELEASE: in target_scsi2_reservation_check()420 case RELEASE: in core_scsi3_pr_seq_non_holder()
243 case RELEASE: what = "RELEASE"; break; in mts_show_command()
381 Bus implements below APIs for RELEASE state which needs to be called by
1731 case RELEASE: in DEF_SCSI_QCMD()2345 scp->cmnd[0] == RELEASE)) { in megaraid_mbox_dpc()
1756 case RELEASE: in gdth_next()2008 else if (scp->cmnd[0] == RELEASE) in gdth_fill_cache_cmd()2782 } else if (scp->cmnd[0] == RELEASE) { in gdth_sync_event()
857 case RELEASE: in mega_build_cmd()1625 cmd->cmnd[0] == RELEASE) ) { in mega_cmd_done()
3650 case RELEASE: in ips_send_cmd()3918 case RELEASE: in ips_chkstatus()
372 Refer to the RELEASE.TXT file distributed as part of this archive for a list of
6 PRODUCTION RELEASE
2038 case RELEASE: in do_scsi_command()
