hesela.devNVMe Abort
NVMe Abort is an administrative command that requests cancellation of an earlier command identified by its submission queue and command identifier.
Base 2.3 distinguishes immediate and deferred abort. After successful Abort completion, DW0 bit 0 is Immediate Abort Not Performed (IANP): zero reports an immediate abort; one means no immediate abort, with later cancellation still possible. Examine the target completion. The immediate-abort boundary forbids target effects after posting the Abort completion except its completion entry; Hesela interprets this as a forward-looking boundary, not rollback. [1]
If deferred abort occurs, the target completes with Command Abort Requested. That status alone does not distinguish immediate from deferred abort; retain the Abort result and completion context. [1]
Base 2.0d instead requires the aborted target's completion before the Abort completion. Do not transfer that ordering to 2.3. Its Abort Command Limit (ACL) counts concurrent Abort commands, not seconds or retries; raw zero encodes one command. [2]
Linux v6.12's PCI driver logs the Abort request status, not DW0 or the target status. Consequently, Abort status: 0x0 alone cannot establish target cancellation. The aborting log precedes request allocation and is not proof that an Abort was submitted. This is source inspection, not a hardware experiment. [3]
Relations
- related
- NVMe, I/O timeout, Retry deduplication