From: Ming Lei <ming.lei@redhat.com> To: Christoph Hellwig <hch@lst.de> Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org, linux-nvme@lists.infradead.org, Chaitanya Kulkarni <chaitanyak@nvidia.com>, Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>, Bart Van Assche <bvanassche@acm.org> Subject: Re: [PATCH V3 6/6] blk-mq: support concurrent queue quiesce/unquiesce Date: Tue, 12 Oct 2021 23:06:51 +0800 [thread overview] Message-ID: <YWWki6An1sOpx3rV@T590> (raw) In-Reply-To: <20211012103010.GA29640@lst.de> On Tue, Oct 12, 2021 at 12:30:10PM +0200, Christoph Hellwig wrote: > On Sat, Oct 09, 2021 at 11:47:13AM +0800, Ming Lei wrote: > > + spin_lock_irqsave(&q->queue_lock, flags); > > + if (!q->quiesce_depth++) > > + blk_queue_flag_set(QUEUE_FLAG_QUIESCED, q); > > We can get rid of the QUEUE_FLAG_QUIESCED flag now and just look > at ->quiesce_depth directly. I'd rather not to do that given we need to check QUEUE_FLAG_QUIESCED in fast path. > > > + spin_lock_irqsave(&q->queue_lock, flags); > > + WARN_ON_ONCE(q->quiesce_depth <= 0); > > + if (q->quiesce_depth > 0 && !--q->quiesce_depth) { > > if (WARN_ON_ONCE(q->quiesce_depth <= 0)) > ; /* oops */ > else if (!--q->quiesce_depth) > run_queue = true; OK. Thanks, Ming
WARNING: multiple messages have this Message-ID (diff)
From: Ming Lei <ming.lei@redhat.com> To: Christoph Hellwig <hch@lst.de> Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org, linux-nvme@lists.infradead.org, Chaitanya Kulkarni <chaitanyak@nvidia.com>, Sagi Grimberg <sagi@grimberg.me>, Keith Busch <kbusch@kernel.org>, Bart Van Assche <bvanassche@acm.org> Subject: Re: [PATCH V3 6/6] blk-mq: support concurrent queue quiesce/unquiesce Date: Tue, 12 Oct 2021 23:06:51 +0800 [thread overview] Message-ID: <YWWki6An1sOpx3rV@T590> (raw) In-Reply-To: <20211012103010.GA29640@lst.de> On Tue, Oct 12, 2021 at 12:30:10PM +0200, Christoph Hellwig wrote: > On Sat, Oct 09, 2021 at 11:47:13AM +0800, Ming Lei wrote: > > + spin_lock_irqsave(&q->queue_lock, flags); > > + if (!q->quiesce_depth++) > > + blk_queue_flag_set(QUEUE_FLAG_QUIESCED, q); > > We can get rid of the QUEUE_FLAG_QUIESCED flag now and just look > at ->quiesce_depth directly. I'd rather not to do that given we need to check QUEUE_FLAG_QUIESCED in fast path. > > > + spin_lock_irqsave(&q->queue_lock, flags); > > + WARN_ON_ONCE(q->quiesce_depth <= 0); > > + if (q->quiesce_depth > 0 && !--q->quiesce_depth) { > > if (WARN_ON_ONCE(q->quiesce_depth <= 0)) > ; /* oops */ > else if (!--q->quiesce_depth) > run_queue = true; OK. Thanks, Ming _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme
next prev parent reply other threads:[~2021-10-12 15:07 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-10-09 3:47 [PATCH V3 0/6] blk-mq: support concurrent queue quiescing Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-09 3:47 ` [PATCH V3 1/6] nvme: add APIs for stopping/starting admin queue Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-09 3:47 ` [PATCH V3 2/6] nvme: apply nvme API to quiesce/unquiesce " Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-09 3:47 ` [PATCH V3 3/6] nvme: prepare for pairing quiescing and unquiescing Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-09 3:47 ` [PATCH V3 4/6] nvme: paring quiesce/unquiesce Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-12 10:36 ` Christoph Hellwig 2021-10-12 10:36 ` Christoph Hellwig 2021-10-12 15:01 ` Ming Lei 2021-10-12 15:01 ` Ming Lei 2021-10-12 15:07 ` Christoph Hellwig 2021-10-12 15:07 ` Christoph Hellwig 2021-10-12 15:17 ` Ming Lei 2021-10-12 15:17 ` Ming Lei 2021-10-13 12:23 ` Sagi Grimberg 2021-10-13 12:23 ` Sagi Grimberg 2021-10-09 3:47 ` [PATCH V3 5/6] nvme: loop: clear NVME_CTRL_ADMIN_Q_STOPPED after admin queue is reallocated Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-09 3:47 ` [PATCH V3 6/6] blk-mq: support concurrent queue quiesce/unquiesce Ming Lei 2021-10-09 3:47 ` Ming Lei 2021-10-12 10:30 ` Christoph Hellwig 2021-10-12 10:30 ` Christoph Hellwig 2021-10-12 15:06 ` Ming Lei [this message] 2021-10-12 15:06 ` Ming Lei 2021-10-12 15:08 ` Christoph Hellwig 2021-10-12 15:08 ` Christoph Hellwig 2021-10-12 15:13 ` Ming Lei 2021-10-12 15:13 ` Ming Lei
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=YWWki6An1sOpx3rV@T590 \ --to=ming.lei@redhat.com \ --cc=axboe@kernel.dk \ --cc=bvanassche@acm.org \ --cc=chaitanyak@nvidia.com \ --cc=hch@lst.de \ --cc=kbusch@kernel.org \ --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: linkBe 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.