Home
last modified time | relevance | path

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

12

/Linux-v4.19/Documentation/translations/ko_KR/
Dmemory-barriers.txt504 ACQUIRE 오퍼레이션은 거의 항상 RELEASE 오퍼레이션과 짝을 지어 사용되어야
508 (6) RELEASE 오퍼레이션.
510 이 타입의 오퍼레이션들도 단방향 투과성 배리어처럼 동작합니다. RELEASE
511 오퍼레이션 앞의 모든 메모리 오퍼레이션들은 RELEASE 오퍼레이션 전에 완료된
513 오퍼레이션들과 smp_store_release() 오퍼레이션도 RELEASE 오퍼레이션의
516 RELEASE 오퍼레이션 뒤의 메모리 오퍼레이션들은 RELEASE 오퍼레이션이
519 ACQUIRE 와 RELEASE 오퍼레이션의 사용은 일반적으로 다른 메모리 배리어의
521 알아두세요). 또한, RELEASE+ACQUIRE 조합은 범용 메모리 배리어처럼 동작할
522 것을 보장하지 -않습니다-. 하지만, 어떤 변수에 대한 RELEASE 오퍼레이션을
523 앞서는 메모리 액세스들의 수행 결과는 이 RELEASE 오퍼레이션을 뒤이어 같은
[all …]
/Linux-v4.19/Documentation/core-api/
Drefcount-vs-atomic.rst49 A RELEASE memory ordering guarantees that all prior loads and
103 * fully unordered --> RELEASE ordering
134 * fully ordered --> RELEASE ordering + control dependency
149 * fully ordered --> RELEASE ordering + control dependency + hold
/Linux-v4.19/Documentation/
Datomic_t.txt159 {}_release: the W of the RMW (or atomic_set) is a RELEASE
197 is a 'typical' RELEASE pattern, the barrier is strictly stronger than
198 a RELEASE. Similarly for something like:
Dmemory-barriers.txt480 An ACQUIRE operation should almost always be paired with a RELEASE
484 (6) RELEASE operations.
487 memory operations before the RELEASE operation will appear to happen
488 before the RELEASE operation with respect to the other components of the
489 system. RELEASE operations include UNLOCK operations and
492 Memory operations that occur after a RELEASE operation may appear to
495 The use of ACQUIRE and RELEASE operations generally precludes the need
497 the subsection "MMIO write barrier"). In addition, a RELEASE+ACQUIRE
500 RELEASE on that same variable are guaranteed to be visible. In other
506 RELEASE acts as a minimal "release" operation.
[all …]
Datomic_bitops.txt67 clear_bit_unlock() which has RELEASE semantics.
/Linux-v4.19/drivers/s390/char/
Dtape_std.h56 #define RELEASE 0xD4 /* 3420 NOP, 3480 REJECT */ macro
/Linux-v4.19/drivers/usb/storage/
Ddebug.c63 case RELEASE: what = "RELEASE"; break; in usb_stor_show_command()
/Linux-v4.19/include/scsi/
Dscsi_proto.h36 #define RELEASE 0x17 macro
/Linux-v4.19/include/trace/events/
Dtarget.h35 scsi_opcode_name(RELEASE), \
Dscsi.h33 scsi_opcode_name(RELEASE), \
/Linux-v4.19/arch/m68k/ifpsp060/
DMISC29 RELEASE FILE VERSIONS:
DCHANGES30 CHANGES SINCE LAST RELEASE:
/Linux-v4.19/tools/lib/traceevent/
Dplugin_scsi.c31 #define RELEASE 0x17 macro
/Linux-v4.19/drivers/usb/image/
Dmicrotek.c243 case RELEASE: what = "RELEASE"; break; in mts_show_command()
/Linux-v4.19/drivers/target/
Dtarget_core_spc.c1313 case RELEASE: in spc_parse_cdb()
Dtarget_core_device.c1179 if (cdb[0] == RELEASE || cdb[0] == RELEASE_10) { in passthrough_parse_cdb()
Dtarget_core_pr.c107 case RELEASE: in target_scsi2_reservation_check()
428 case RELEASE: in core_scsi3_pr_seq_non_holder()
/Linux-v4.19/Documentation/driver-api/soundwire/
Dstream.rst347 Bus implements below APIs for RELEASE state which needs to be called by
/Linux-v4.19/drivers/scsi/megaraid/
Dmegaraid_mbox.c1752 case RELEASE: in DEF_SCSI_QCMD()
2391 scp->cmnd[0] == RELEASE)) { in megaraid_mbox_dpc()
/Linux-v4.19/drivers/scsi/
Dmegaraid.c862 case RELEASE: in mega_build_cmd()
1630 cmd->cmnd[0] == RELEASE) ) { in mega_cmd_done()
Dgdth.c2206 case RELEASE: in gdth_next()
2461 else if (scp->cmnd[0] == RELEASE) in gdth_fill_cache_cmd()
3361 } else if (scp->cmnd[0] == RELEASE) { in gdth_sync_event()
Dips.c3650 case RELEASE: in ips_send_cmd()
3918 case RELEASE: in ips_chkstatus()
/Linux-v4.19/Documentation/networking/
Dcs89x0.txt372 Refer to the RELEASE.TXT file distributed as part of this archive for a list of
/Linux-v4.19/Documentation/scsi/
DBusLogic.txt6 PRODUCTION RELEASE
/Linux-v4.19/drivers/staging/rts5208/
Drtsx_scsi.c89 case RELEASE: in scsi_show_command()

12