diff options
author | Martin Belanger <martin.belanger@dell.com> | 2022-02-08 22:33:45 +0300 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2022-02-28 14:45:06 +0300 |
commit | 20d64911e7580f7e29c0086d67860c18307377d7 (patch) | |
tree | 5d974ba54f77d4783b9eda5d2e40b3f2c401af14 /include | |
parent | 89377bc1975c2993bde4a498a3a4e5817ac0ae2c (diff) | |
download | linux-20d64911e7580f7e29c0086d67860c18307377d7.tar.xz |
nvme: send uevent on connection up
When connectivity with a controller is lost, the driver will keep
trying to reconnect once every 10 sec. When connection is restored,
user-space apps need to be informed so that they can take proper
action. For example, TP8010 introduces the DIM PDU, which is used to
register with a discovery controller (DC). The DIM PDU is sent from
user-space. The DIM PDU must be sent every time a connection is
established with a DC. Therefore, the kernel must tell user-space apps
when connection is restored so that registration can happen.
The uevent sent is a "change" uevent with environmental data
set to: "NVME_EVENT=connected".
Signed-off-by: Martin Belanger <martin.belanger@dell.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
Reviewed-by: John Meneghini <jmeneghi@redhat.com>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions