| UID | tech.root | title | ms.date | ms.topic | targetos | description | req.construct-type | req.ddi-compliance | req.dll | req.header | req.include-header | req.kmdf-ver | req.lib | req.max-support | req.redist | req.target-min-winverclnt | req.target-min-winversvr | req.target-type | req.typenames | req.umdf-ver | req.unicode-ansi | topic_type | api_type | api_location | api_name | f1_keywords | dev_langs | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
NS:nvme._NVME_TELEMETRY_HOST_INITIATED_LOG |
fs |
NVME_TELEMETRY_HOST_INITIATED_LOG |
02/19/2021 |
language-reference |
Windows |
Contains fields that specify the information in a Telemetry Host-Initiated Log page. |
structure |
nvme.h |
Windows 10 |
NVME_TELEMETRY_HOST_INITIATED_LOG, *PNVME_TELEMETRY_HOST_INITIATED_LOG |
|
|
|
|
|
|
Contains fields that specify the information in a Telemetry Host-Initiated Log page.
The NVME_RESERVATION_NOTIFICATION_LOG structure is returned by the Get Log Page command. For more information, see NVME_CDW10_GET_LOG_PAGE.
Indicates the log identifier.
Bytes 1-4 are reserved.
Indicates an IEEE Organizationally Unique Identifier (OUI) that is the Organization ID.
Bytes 8-9 indicate the last block of Area 1.
Bytes 10-11 indicate the last block of Area 2.
Bytes 12-13 indicate the last block of Area 3.
Bytes 14-381 are reserved.
Byte 382 indicates whether controller initiated data is available.
Byte 383 indicates the generation number of controller initiated data when it is available.
Bytes 384-511 indicate the reason identifier.
All NVMe Telemetry Data Blocks are 512 bytes in size.