diff options
| author | Hannes Reinecke <[email protected]> | 2022-12-08 08:49:20 +0100 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2023-02-01 14:21:58 +0100 |
| commit | 0686fb3cc535c4c1685553c56f4efe3eeee57b09 (patch) | |
| tree | 7e00b4217058e162aad338b4108186537e0595e2 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 2d97930d74b12467fd5f48d8560e48c1cf5edcb1 (diff) | |
nvme-fabrics: clarify AUTHREQ result handling
The NVMe 2.0 spec defines the ATR and ASCR bits in the AUTHREQ
connect response field to be mutually exclusive. So to clarify the
handling here switch the AUTHREQ handling to use the bit definitions
and check for both bits.
And while we're at it, add a message to the user that secure
concatenation is not supported (yet).
Suggested-by: Mark Lehrer <[email protected]>
Signed-off-by: Hannes Reinecke <[email protected]>
Reviewed-by: Sagi Grimberg <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions