From: Ming Lei <ming.lei@redhat.com>
To: Chao Leng <lengchao@huawei.com>
Cc: linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
kbusch@kernel.org, axboe@fb.com, hch@lst.de, sagi@grimberg.me
Subject: Re: [PATCH v2 0/3] reduce quiesce time for lots of name spaces
Date: Mon, 10 Aug 2020 11:15:47 +0800 [thread overview]
Message-ID: <20200810031547.GB2202641@T590> (raw)
In-Reply-To: <61a78a78-73aa-1c67-1e8c-eae8f7c3a4e0@huawei.com>
On Mon, Aug 10, 2020 at 10:17:04AM +0800, Chao Leng wrote:
>
>
> On 2020/8/7 21:49, Ming Lei wrote:
> > On Fri, Aug 07, 2020 at 05:05:59PM +0800, Chao Leng wrote:
> > > nvme_stop_queues quiesce queues for all name spaces, now quiesce one by
> > > one, if there is lots of name spaces, sync wait long time(more than 10s).
> > > Multipath can not fail over to retry quickly, cause io pause long time.
> > > This is not expected.
> > > To reduce quiesce time, we introduce async mechanism for sync SRCUs
> > > and quiesce queue.
> > >
> >
> > Frankly speaking, I prefer to replace SRCU with percpu_refcount:
> >
> > - percpu_refcount has much less memory footprint than SRCU, so we can simply
> > move percpu_refcount into request_queue, instead of adding more bytes
> > into each hctx by this patch
> >
> > - percpu_ref_get()/percpu_ref_put() isn't slower than srcu_read_lock()/srcu_read_unlock().
> >
> > - with percpu_refcount, we can remove 'srcu_idx' from hctx_lock/hctx_unlock()
> IO pause long time if fail over, this is a serios problem. we need fix
> it as soon as possible. SRCU is just used for blocking queue,
The issue has been long time since SRCU is taken, not sure if it is
something urgent.
> non blocking queue need 0 bytes. So more bytes(just 24 bytes) is not
> waste.
>
> About using per_cpu to replace SRCU, I suggest separate discussion.
> Can you show the patch? This will make it easier to discuss.
https://lore.kernel.org/linux-block/20200728134938.1505467-1-ming.lei@redhat.com/
Thanks,
Ming
next prev parent reply other threads:[~2020-08-10 3:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-07 9:05 [PATCH v2 0/3] reduce quiesce time for lots of name spaces Chao Leng
2020-08-07 13:49 ` Ming Lei
2020-08-07 16:37 ` Sagi Grimberg
2020-08-10 2:17 ` Chao Leng
2020-08-10 3:15 ` Ming Lei [this message]
2020-08-11 3:13 ` Chao Leng
2020-08-11 20:53 ` Sagi Grimberg
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=20200810031547.GB2202641@T590 \
--to=ming.lei@redhat.com \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--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