From: Christoph Hellwig <hch@lst.de>
To: Chao Leng <lengchao@huawei.com>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
hch@lst.de, sagi@grimberg.me, kbusch@kernel.org, axboe@kernel.dk
Subject: Re: [PATCH 0/3] improve nvme quiesce time for large amount of namespaces
Date: Fri, 29 Jul 2022 16:26:05 +0200 [thread overview]
Message-ID: <20220729142605.GA395@lst.de> (raw)
In-Reply-To: <20220729073948.32696-1-lengchao@huawei.com>
Why can't we have a per-tagset quiesce flag and just wait for the
one? That also really nicely supports the problem with changes in
the namespace list during that time.
next prev parent reply other threads:[~2022-07-29 14:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 7:39 [PATCH 0/3] improve nvme quiesce time for large amount of namespaces Chao Leng
2022-07-29 7:39 ` [PATCH 1/3] blk-mq: delete unnecessary comments Chao Leng
2022-07-29 7:39 ` [PATCH 2/3] nvme: improve the quiesce time for non blocking transports Chao Leng
2022-07-29 7:39 ` [PATCH 3/3] nvme: improve the quiesce time for " Chao Leng
2022-07-29 14:26 ` Christoph Hellwig [this message]
2022-07-30 0:39 ` [PATCH 0/3] improve nvme quiesce time for large amount of namespaces Chao Leng
2022-07-31 10:23 ` Sagi Grimberg
2022-08-01 1:45 ` Chao Leng
2022-08-02 13:38 ` Christoph Hellwig
2022-10-10 8:46 ` Chao Leng
2022-10-12 6:37 ` Sagi Grimberg
2022-10-12 8:43 ` Chao Leng
2022-10-12 11:13 ` Sagi Grimberg
2022-10-13 1:37 ` Chao Leng
2022-10-13 2:06 ` Chao Leng
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=20220729142605.GA395@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=lengchao@huawei.com \
--cc=linux-block@vger.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;
as well as URLs for NNTP newsgroup(s).