nvme: consolidate setting the tagset flags
authorChristoph Hellwig <hch@lst.de>
Wed, 30 Nov 2022 16:19:50 +0000 (17:19 +0100)
committerChristoph Hellwig <hch@lst.de>
Wed, 7 Dec 2022 14:02:20 +0000 (15:02 +0100)
commitdb45e1a5ddccc034eb60d62fc5352022d7963ae2
tree56632abad29089331d091614fe4d7c898c1441e5
parentdcef77274ae52136925287b6b59d5c6e6a4adfb9
nvme: consolidate setting the tagset flags

All nvme transports should be using the same flags for their tagsets,
with the exception for the blocking flag that should only be set for
transports that can block in ->queue_rq.

Add a NVME_F_BLOCKING flag to nvme_ctrl_ops to control the blocking
behavior and lift setting the flags into nvme_alloc_{admin,io}_tag_set.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>
drivers/nvme/host/core.c
drivers/nvme/host/fc.c
drivers/nvme/host/nvme.h
drivers/nvme/host/rdma.c
drivers/nvme/host/tcp.c
drivers/nvme/target/loop.c