Skip to content

Latest commit

 

History

History
96 lines (69 loc) · 3.26 KB

ns-minitape-write_using_token_header.md

File metadata and controls

96 lines (69 loc) · 3.26 KB
UID title description tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NS:minitape.WRITE_USING_TOKEN_HEADER
WRITE_USING_TOKEN_HEADER (minitape.h)
The WRITE_USING_TOKEN_HEADER structure (minitape.h) describes the destination data locations for an offload write data operation.
storage
09/23/2022
WRITE_USING_TOKEN_HEADER structure
*PWRITE_USING_TOKEN_HEADER, PWRITE_USING_TOKEN_HEADER, PWRITE_USING_TOKEN_HEADER structure pointer [Storage Devices], WRITE_USING_TOKEN_HEADER, WRITE_USING_TOKEN_HEADER structure [Storage Devices], scsi/PWRITE_USING_TOKEN_HEADER, scsi/WRITE_USING_TOKEN_HEADER, storage.write_using_token_header
minitape.h
Scsi.h, Minitape.h, Storport.h
Windows
Available starting with Windows 8.
Windows
WRITE_USING_TOKEN_HEADER, *PWRITE_USING_TOKEN_HEADER
PWRITE_USING_TOKEN_HEADER
minitape/PWRITE_USING_TOKEN_HEADER
WRITE_USING_TOKEN_HEADER
minitape/WRITE_USING_TOKEN_HEADER
APIRef
kbSyntax
HeaderDef
scsi.h
PWRITE_USING_TOKEN_HEADER
WRITE_USING_TOKEN_HEADER

-description

The WRITE_USING_TOKEN_HEADER structure describes the destination data locations for an offload write data operation. The offload write data operation described by this structure is associated with a token representation of data (ROD).

-struct-fields

-field WriteUsingTokenDataLength

The length of this structure beginning with the Immediate parameter and include all of the elements of the BlockDeviceRangeDescriptor array.

-field Immediate

If set, the status of the WRITE USING TOKEN command is returned immediately after receipt and validation of the token ROD and range descriptors. Otherwise, status is returned after all command processing is complete.

-field Reserved1

Reserved bits.

-field Reserved2

Reserved.

-field BlockOffsetIntoToken

The offset, in logical blocks, in the ROD for Token indicating the start of the source data for the offload write data operation.

-field Token

A token created by a previous the POPULATE TOKEN command operation.

-field Reserved3

Reserved.

-field BlockDeviceRangeDescriptorListLength

The length, in bytes, for all of the BLOCK_DEVICE_RANGE_DESCRIPTOR structures in the BlockDeviceRangeDescriptor array.

-field BlockDeviceRangeDescriptor

An array of BLOCK_DEVICE_RANGE_DESCRIPTOR structures which describe the destination data blocks for the offload write data transfer.

-remarks

All multibyte values are in big endian format. Prior to setting, these values must be converted from the endian format of the current platform.

-see-also

BLOCK_DEVICE_RANGE_DESCRIPTOR

POPULATE_TOKEN_HEADER