From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCH 0/4] nvme: start keep-alive after admin queue setup
Date: Fri, 20 Oct 2023 16:25:56 +0200 [thread overview]
Message-ID: <20231020142600.47246-1-hare@suse.de> (raw)
Hi all,
Setting up I/O queues might take quite some time on larger and/or
busy setups, so KATO might expire on the admin queue before all
I/O queues can be setup.
This patchset fixes this issue by moving the calls to starting
and stopping KATO into the quiesce/unquiesce functions.
That requires some refactoring/alignment with some transport
drivers which do not always quiesce and unquiesce the admin
queue.
As usual, comments and reviews are welcome.
Hannes Reinecke (4):
nvme-fc: add missing quiesce in nvme_fc_create_association()
nvme-pci: unquiesce admin queue before nvme_init_ctrl_finish()
nvme-loop: quiesce admin queue on failure
nvme: start keep-alive after admin queue setup
drivers/nvme/host/apple.c | 4 ++--
drivers/nvme/host/core.c | 7 ++++---
drivers/nvme/host/fc.c | 16 +++++++++-------
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/pci.c | 9 ++++++---
drivers/nvme/host/rdma.c | 6 +++---
drivers/nvme/host/tcp.c | 6 +++---
drivers/nvme/target/loop.c | 6 ++++--
8 files changed, 32 insertions(+), 24 deletions(-)
--
2.35.3
next reply other threads:[~2023-10-20 14:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 14:25 Hannes Reinecke [this message]
2023-10-20 14:25 ` [PATCH 1/4] nvme-fc: add missing quiesce in nvme_fc_create_association() Hannes Reinecke
2023-10-20 14:25 ` [PATCH 2/4] nvme-pci: unquiesce admin queue before nvme_init_ctrl_finish() Hannes Reinecke
2023-10-20 14:25 ` [PATCH 3/4] nvme-loop: quiesce admin queue on failure Hannes Reinecke
2023-10-20 14:26 ` [PATCH 4/4] nvme: start keep-alive after admin queue setup Hannes Reinecke
2023-10-20 15:30 ` [PATCH 0/4] " Keith Busch
2023-10-23 9:54 ` Hannes Reinecke
2023-10-23 23:16 ` Keith Busch
2023-10-24 5:30 ` Hannes Reinecke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20231020142600.47246-1-hare@suse.de \
--to=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox