Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Smart <jsmart2021@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Sagi Grimberg <sagi@grimberg.me>, Chao Leng <lengchao@huawei.com>,
	linux-nvme@lists.infradead.org, axboe@fb.com, hch@lst.de
Subject: Re: [PATCH] nvme-fabrics: fix crash for no IO queues
Date: Tue, 16 Mar 2021 17:19:13 -0700	[thread overview]
Message-ID: <ced0b93a-3867-0756-bdd9-ead73c34b2e8@gmail.com> (raw)
In-Reply-To: <20210316212559.GA4161557@dhcp-10-100-145-180.wdc.com>


> 
> One more question: if the controller is in such a bad way that it will
> never create IO queues without additional intervention, will this
> behavior have the driver schedule reconnect indefinitely?
> 

No.. in fabrics, there is a max controller reconnect timeout that will 
expire (dflt 600s), stop the reconnect attempts and delete the controller.

-- james

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

  parent reply	other threads:[~2021-03-17  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  0:55 [PATCH] nvme-fabrics: fix crash for no IO queues Chao Leng
2021-03-05 20:58 ` Sagi Grimberg
2021-03-08  1:30   ` Chao Leng
2021-03-15 17:08     ` Sagi Grimberg
2021-03-16  1:23       ` Chao Leng
2021-03-16  2:02         ` Keith Busch
2021-03-16  5:08           ` Sagi Grimberg
2021-03-16 20:57             ` James Smart
2021-03-16 21:25               ` Keith Busch
2021-03-16 23:52                 ` Sagi Grimberg
2021-03-17  0:19                 ` James Smart [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-03-03  2:53 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=ced0b93a-3867-0756-bdd9-ead73c34b2e8@gmail.com \
    --to=jsmart2021@gmail.com \
    --cc=axboe@fb.com \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=lengchao@huawei.com \
    --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