All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	James Smart <james.smart@broadcom.com>,
	Keith Busch <kbusch@kernel.org>, Ming Lei <ming.lei@redhat.com>,
	Wen Xiong <wenxiong@us.ibm.com>,
	James Smart <jsmart2021@gmail.com>
Subject: Re: [PATCH v4 6/8] nvme-fc: fix controller reset hang during traffic
Date: Tue, 10 Aug 2021 18:05:04 -0700	[thread overview]
Message-ID: <d43f83cf-a3cd-df16-5af8-1f530b25d1cc@grimberg.me> (raw)
In-Reply-To: <20210804080847.bajae2twtnmccvq7@beryllium.lan>


> On Wed, Aug 04, 2021 at 09:23:49AM +0200, Hannes Reinecke wrote:
>> There still is now an imbalance, as we're always calling
>> 'nvme_unfreeze()' (irrespective on the number of queues), but will only
>> call 'nvme_start_freeze()' if we have more than one queue.
>>
>> This might lead to an imbalance on the mq_freeze_depth counter.
>> Wouldn't it be better to move the call to 'nvme_start_freeze()' out of
>> the if() condition to avoid the imbalance?
> 
> What about something like nmve_is_frozen() which would avoid the tracking
> of the queue state open coded as it is right?

Why is there a conditional freeze?

WARNING: multiple messages have this Message-ID (diff)
From: Sagi Grimberg <sagi@grimberg.me>
To: Daniel Wagner <dwagner@suse.de>, Hannes Reinecke <hare@suse.de>
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	James Smart <james.smart@broadcom.com>,
	Keith Busch <kbusch@kernel.org>, Ming Lei <ming.lei@redhat.com>,
	Wen Xiong <wenxiong@us.ibm.com>,
	James Smart <jsmart2021@gmail.com>
Subject: Re: [PATCH v4 6/8] nvme-fc: fix controller reset hang during traffic
Date: Tue, 10 Aug 2021 18:05:04 -0700	[thread overview]
Message-ID: <d43f83cf-a3cd-df16-5af8-1f530b25d1cc@grimberg.me> (raw)
In-Reply-To: <20210804080847.bajae2twtnmccvq7@beryllium.lan>


> On Wed, Aug 04, 2021 at 09:23:49AM +0200, Hannes Reinecke wrote:
>> There still is now an imbalance, as we're always calling
>> 'nvme_unfreeze()' (irrespective on the number of queues), but will only
>> call 'nvme_start_freeze()' if we have more than one queue.
>>
>> This might lead to an imbalance on the mq_freeze_depth counter.
>> Wouldn't it be better to move the call to 'nvme_start_freeze()' out of
>> the if() condition to avoid the imbalance?
> 
> What about something like nmve_is_frozen() which would avoid the tracking
> of the queue state open coded as it is right?

Why is there a conditional freeze?

_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  reply	other threads:[~2021-08-11  1:05 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02 11:26 [PATCH RESEND v4 0/8] Handle update hardware queues and queue freeze more carefully Daniel Wagner
2021-08-02 11:26 ` Daniel Wagner
2021-08-02 11:26 ` [PATCH v4 1/8] nvme-fc: Update hardware queues before using them Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 19:34   ` Himanshu Madhani
2021-08-02 19:34     ` Himanshu Madhani
2021-08-02 11:26 ` [PATCH v4 2/8] nvme-tcp: Update number of " Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-06 19:57   ` Sagi Grimberg
2021-08-06 19:57     ` Sagi Grimberg
2021-08-09  8:52     ` Daniel Wagner
2021-08-09  8:52       ` Daniel Wagner
2021-08-11  1:00       ` Sagi Grimberg
2021-08-11  1:00         ` Sagi Grimberg
2021-08-11  1:07         ` Keith Busch
2021-08-11  1:07           ` Keith Busch
2021-08-11  5:57           ` Sagi Grimberg
2021-08-11  5:57             ` Sagi Grimberg
2021-08-11 10:25             ` Daniel Wagner
2021-08-11 10:25               ` Daniel Wagner
2021-08-02 11:26 ` [PATCH v4 3/8] nvme-rdma: " Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 11:26 ` [PATCH v4 4/8] nvme-fc: Wait with a timeout for queue to freeze Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 19:36   ` Himanshu Madhani
2021-08-02 19:36     ` Himanshu Madhani
2021-08-02 11:26 ` [PATCH v4 5/8] nvme-fc: avoid race between time out and tear down Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 19:38   ` Himanshu Madhani
2021-08-02 19:38     ` Himanshu Madhani
2021-08-02 11:26 ` [PATCH v4 6/8] nvme-fc: fix controller reset hang during traffic Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 19:39   ` Himanshu Madhani
2021-08-02 19:39     ` Himanshu Madhani
2021-08-04  7:23   ` Hannes Reinecke
2021-08-04  7:23     ` Hannes Reinecke
2021-08-04  8:08     ` Daniel Wagner
2021-08-04  8:08       ` Daniel Wagner
2021-08-11  1:05       ` Sagi Grimberg [this message]
2021-08-11  1:05         ` Sagi Grimberg
2021-08-11 10:30         ` Daniel Wagner
2021-08-11 10:30           ` Daniel Wagner
2021-08-12 20:03     ` James Smart
2021-08-12 20:03       ` James Smart
2021-08-18 11:43       ` Daniel Wagner
2021-08-18 11:43         ` Daniel Wagner
2021-08-18 11:49         ` Daniel Wagner
2021-08-18 11:49           ` Daniel Wagner
2021-08-02 11:26 ` [PATCH v4 7/8] nvme-tcp: Unfreeze queues on reconnect Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-02 11:26 ` [PATCH v4 8/8] nvme-rdma: " Daniel Wagner
2021-08-02 11:26   ` Daniel Wagner
2021-08-04  7:25   ` Hannes Reinecke
2021-08-04  7:25     ` Hannes Reinecke
2021-08-06 19:59   ` Sagi Grimberg
2021-08-06 19:59     ` Sagi Grimberg
2021-08-09  8:58     ` Daniel Wagner
2021-08-09  8:58       ` Daniel Wagner
  -- strict thread matches above, loose matches on Subject: below --
2021-08-02  9:14 [PATCH v4 0/8] Handle update hardware queues and queue freeze more carefully Daniel Wagner
2021-08-02  9:14 ` [PATCH v4 6/8] nvme-fc: fix controller reset hang during traffic Daniel Wagner

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=d43f83cf-a3cd-df16-5af8-1f530b25d1cc@grimberg.me \
    --to=sagi@grimberg.me \
    --cc=dwagner@suse.de \
    --cc=hare@suse.de \
    --cc=james.smart@broadcom.com \
    --cc=jsmart2021@gmail.com \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=ming.lei@redhat.com \
    --cc=wenxiong@us.ibm.com \
    /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.