nvme/libnvme
1
0
Fork 0
Code Issues Activity

Merging upstream version 1.3.

Browse source 
Signed-off-by: Daniel Baumann <daniel@debian.org>
This commit is contained in:
Daniel Baumann 2025-02-16 10:06:51 +01:00
parent 34cf2bc5f8
commit ae07fb4ed6
Signed by: daniel
GPG key ID: FBB4F0E80A80222F
803 changed files with 4523 additions and 1325 deletions
Download patch file Download diff file Expand all files Collapse all files

11
doc/mi.rst.in
View file

@ -13,6 +13,17 @@ Most of the MI API is transport-agnostic, except for the endpoint constructor
functions. Once an endpoint object (``nvme_mi_ep_t``) is created, the generic
functions can be used to manage it.
When endpoints are created (through one of the transport-specific functions,
like ``nvme_mi_open_mctp()``), the endpoint hardware will be probed to
see if any device-specific workarounds ("quirks") are required. This is
implemented as an Identify Controller command, requesting a small amount of
data on controller ID 0.
To suppress this probe, the ``LIBNVME_MI_PROBE_ENABLED`` environment var can be
set. Values of ``0``, ``false`` and ``disabled`` will disable the probe, and no
quirks will be applied. Other values, or an unset environment variable, will
enable the probe.
MCTP Transport
--------------