WRITE_USING_TOKEN_HEADER - NtDoc
Native API online documentation, based on the System Informer
(formerly Process Hacker) phnt
headers
// minitape.h
typedef struct {
UCHAR WriteUsingTokenDataLength[2];
UCHAR Immediate : 1;
UCHAR Reserved1 : 7;
UCHAR Reserved2[5];
UCHAR BlockOffsetIntoToken[8];
UCHAR Token[BLOCK_DEVICE_TOKEN_SIZE];
UCHAR Reserved3[6];
UCHAR BlockDeviceRangeDescriptorListLength[2];
UCHAR BlockDeviceRangeDescriptor[ANYSIZE_ARRAY];
} WRITE_USING_TOKEN_HEADER, *PWRITE_USING_TOKEN_HEADER;
View the official Windows Driver Kit DDI reference// scsi.h
typedef struct {
UCHAR WriteUsingTokenDataLength[2];
UCHAR Immediate : 1;
UCHAR Reserved1 : 7;
UCHAR Reserved2[5];
UCHAR BlockOffsetIntoToken[8];
UCHAR Token[BLOCK_DEVICE_TOKEN_SIZE];
UCHAR Reserved3[6];
UCHAR BlockDeviceRangeDescriptorListLength[2];
UCHAR BlockDeviceRangeDescriptor[ANYSIZE_ARRAY];
} WRITE_USING_TOKEN_HEADER, *PWRITE_USING_TOKEN_HEADER;
View the official Windows Driver Kit DDI reference// storport.h
typedef struct {
UCHAR WriteUsingTokenDataLength[2];
UCHAR Immediate : 1;
UCHAR Reserved1 : 7;
UCHAR Reserved2[5];
UCHAR BlockOffsetIntoToken[8];
UCHAR Token[BLOCK_DEVICE_TOKEN_SIZE];
UCHAR Reserved3[6];
UCHAR BlockDeviceRangeDescriptorListLength[2];
UCHAR BlockDeviceRangeDescriptor[ANYSIZE_ARRAY];
} WRITE_USING_TOKEN_HEADER, *PWRITE_USING_TOKEN_HEADER;
View the official Windows Driver Kit DDI referenceNo description available.
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).
WriteUsingTokenDataLengthThe length of this structure beginning with the Immediate parameter and include all of the elements of the BlockDeviceRangeDescriptor array.
ImmediateIf 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.
Reserved1Reserved bits.
Reserved2Reserved.
BlockOffsetIntoTokenThe offset, in logical blocks, in the ROD for Token indicating the start of the source data for the offload write data operation.
TokenA token created by a previous the POPULATE TOKEN command operation.
Reserved3Reserved.
BlockDeviceRangeDescriptorListLengthThe length, in bytes, for all of the BLOCK_DEVICE_RANGE_DESCRIPTOR structures in the BlockDeviceRangeDescriptor array.
BlockDeviceRangeDescriptorAn array of BLOCK_DEVICE_RANGE_DESCRIPTOR structures which describe the destination data blocks for the offload write data transfer.
All multibyte values are in big endian format. Prior to setting, these values must be converted from the endian format of the current platform.
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).
WriteUsingTokenDataLengthThe length of this structure beginning with the Immediate parameter and include all of the elements of the BlockDeviceRangeDescriptor array.
ImmediateIf 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.
Reserved1Reserved bits.
Reserved2Reserved.
BlockOffsetIntoTokenThe offset, in logical blocks, in the ROD for Token indicating the start of the source data for the offload write data operation.
TokenA token created by a previous the POPULATE TOKEN command operation.
Reserved3Reserved.
BlockDeviceRangeDescriptorListLengthThe length, in bytes, for all of the BLOCK_DEVICE_RANGE_DESCRIPTOR structures in the BlockDeviceRangeDescriptor array.
BlockDeviceRangeDescriptorAn array of BLOCK_DEVICE_RANGE_DESCRIPTOR structures which describe the destination data blocks for the offload write data transfer.
All multibyte values are in big endian format. Prior to setting, these values must be converted from the endian format of the current platform.
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).
WriteUsingTokenDataLengthThe length of this structure beginning with the Immediate parameter and include all of the elements of the BlockDeviceRangeDescriptor array.
ImmediateIf 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.
Reserved1Reserved bits.
Reserved2Reserved.
BlockOffsetIntoTokenThe offset, in logical blocks, in the ROD for Token indicating the start of the source data for the offload write data operation.
TokenA token created by a previous the POPULATE TOKEN command operation.
Reserved3Reserved.
BlockDeviceRangeDescriptorListLengthThe length, in bytes, for all of the BLOCK_DEVICE_RANGE_DESCRIPTOR structures in the BlockDeviceRangeDescriptor array.
BlockDeviceRangeDescriptorAn array of BLOCK_DEVICE_RANGE_DESCRIPTOR structures which describe the destination data blocks for the offload write data transfer.
All multibyte values are in big endian format. Prior to setting, these values must be converted from the endian format of the current platform.