From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@lst.de>
Cc: Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, Hannes Reinecke <hare@suse.de>
Subject: [PATCHv2 0/3] nvme: start keep-alive after admin queue setup
Date: Tue, 24 Oct 2023 08:13:34 +0200 [thread overview]
Message-ID: <20231024061337.35621-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 call to start keep-alive
into the ->init_ctrl_finish() callback, and move the call to stop
keep-alives into nvme_cancel_admin_tagset().
As usual, comments and reviews are welcome.
Changes to the original version:
- Reworked to use nvme_cancel_admin_tagset()
Hannes Reinecke (3):
nvme-tcp: avoid open-coding nvme_tcp_teardown_admin_queue()
nvme-loop: always quiesce and cancel commands before destroying admin
q
nvme: start keep-alive after admin queue setup
drivers/nvme/host/core.c | 6 +++---
drivers/nvme/host/fc.c | 6 ++++++
drivers/nvme/host/tcp.c | 6 +-----
drivers/nvme/target/loop.c | 4 ++++
4 files changed, 14 insertions(+), 8 deletions(-)
--
2.35.3
next reply other threads:[~2023-10-24 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 6:13 Hannes Reinecke [this message]
2023-10-24 6:13 ` [PATCH 1/3] nvme-tcp: avoid open-coding nvme_tcp_teardown_admin_queue() Hannes Reinecke
2023-10-24 6:13 ` [PATCH 2/3] nvme-loop: always quiesce and cancel commands before destroying admin q Hannes Reinecke
2023-10-24 6:13 ` [PATCH 3/3] nvme: start keep-alive after admin queue setup Hannes Reinecke
2023-11-06 17:17 ` Keith Busch
2023-11-20 13:39 ` Sagi Grimberg
2023-11-20 14:19 ` Hannes Reinecke
2023-11-20 14:25 ` Sagi Grimberg
2023-11-20 15:05 ` Hannes Reinecke
2023-11-20 19:03 ` Sagi Grimberg
2023-11-20 16:01 ` Hannes Reinecke
2023-11-20 19:05 ` Sagi Grimberg
2023-11-21 7:29 ` Hannes Reinecke
2023-11-21 9:16 ` Sagi Grimberg
2023-10-26 16:00 ` [PATCHv2 0/3] " Mark O'Donovan
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=20231024061337.35621-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