From: Ming Lei <ming.lei@redhat.com>
To: Ismael Luceno <iluceno@suse.de>
Cc: Enzo Matsumiya <ematsumiya@suse.com>,
Sagi Grimberg <sagi@grimberg.me>, Chao Leng <lengchao@huawei.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH V2 4/5] nvme: quiesce namespace queue in parallel
Date: Tue, 7 Jun 2022 22:03:40 +0800 [thread overview]
Message-ID: <Yp9avMfGDsOLIXeG@T590> (raw)
In-Reply-To: <20220607132118.0bbb230b@pirotess>
On Tue, Jun 07, 2022 at 01:21:18PM +0200, Ismael Luceno wrote:
> Hi Ming,
>
> Has this patch been dropped/abandoned?
Hi Ismael,
The whole patchset wasn't be accepted if I remember correctly, but
finally we moved srcu out of hctx in another patchset.
If you think the patch of 'nvme: quiesce namespace queue in parallel'
is useful, please provide a bit info about your case, then we may
figure out similar patch if it is necessary.
Thanks,
Ming
next prev parent reply other threads:[~2022-06-07 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-30 7:37 [PATCH V2 0/5] blk-mq: quiesce improvement Ming Lei
2021-11-30 7:37 ` [PATCH V2 1/5] blk-mq: remove hctx_lock and hctx_unlock Ming Lei
2021-11-30 14:42 ` kernel test robot
2021-11-30 14:42 ` kernel test robot
2021-12-05 13:16 ` [blk] 4575a8b36e: WARNING:at_kernel/sched/core.c:#__might_sleep kernel test robot
2021-12-05 13:16 ` kernel test robot
2021-11-30 7:37 ` [PATCH V2 2/5] blk-mq: move srcu from blk_mq_hw_ctx to request_queue Ming Lei
2021-11-30 7:37 ` [PATCH V2 3/5] blk-mq: add helper of blk_mq_shared_quiesce_wait() Ming Lei
2021-11-30 7:37 ` [PATCH V2 4/5] nvme: quiesce namespace queue in parallel Ming Lei
2021-11-30 7:37 ` [PATCH V2 5/5] scsi: use blk-mq quiesce APIs to implement scsi_host_block Ming Lei
2022-06-07 11:21 ` [PATCH V2 4/5] nvme: quiesce namespace queue in parallel Ismael Luceno
2022-06-07 14:03 ` Ming Lei [this message]
2022-07-06 15:37 ` Ismael Luceno
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=Yp9avMfGDsOLIXeG@T590 \
--to=ming.lei@redhat.com \
--cc=ematsumiya@suse.com \
--cc=iluceno@suse.de \
--cc=lengchao@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.