diff options
| author | Hannes Reinecke <hare@suse.de> | 2021-04-16 13:46:20 +0200 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2021-04-21 19:13:15 +0200 |
| commit | a70b81bd4d9d2d6c05cfe6ef2a10bccc2e04357a (patch) | |
| tree | b8bf44fd9e9a4f1d7a8c2cc34d10743e33490af4 /kernel/trace/trace_recursion_record.c | |
| parent | 8f864c595bed20ef85fef3e7314212b73800d51d (diff) | |
nvme: sanitize KATO setting
According to the NVMe base spec the KATO commands should be sent
at half of the KATO interval, to properly account for round-trip
times.
As we now will only ever send one KATO command per connection we
can easily use the recommended values.
This also fixes a potential issue where the request timeout for
the KATO command does not match the value in the connect command,
which might be causing spurious connection drops from the target.
Signed-off-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'kernel/trace/trace_recursion_record.c')
0 files changed, 0 insertions, 0 deletions