diff options
| author | Martin George <marting@netapp.com> | 2021-02-11 20:58:26 +0300 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2021-03-05 15:41:03 +0300 |
| commit | 32feb6de47242e54692eceab52cfae8616aa0518 (patch) | |
| tree | d5aac1927c9392e65ab94242e617ee5eca0c2343 /drivers/ipack/ipack.c | |
| parent | 78570f8873c8cd44c12714c7fa7db2601ec5617d (diff) | |
| download | linux-32feb6de47242e54692eceab52cfae8616aa0518.tar.xz | |
nvme-fabrics: fix kato initialization
Currently kato is initialized to NVME_DEFAULT_KATO for both
discovery & i/o controllers. This is a problem specifically
for non-persistent discovery controllers since it always ends
up with a non-zero kato value. Fix this by initializing kato
to zero instead, and ensuring various controllers are assigned
appropriate kato values as follows:
non-persistent controllers - kato set to zero
persistent controllers - kato set to NVMF_DEV_DISC_TMO
(or any positive int via nvme-cli)
i/o controllers - kato set to NVME_DEFAULT_KATO
(or any positive int via nvme-cli)
Signed-off-by: Martin George <marting@netapp.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'drivers/ipack/ipack.c')
0 files changed, 0 insertions, 0 deletions