From: hch@lst.de (Christoph Hellwig)
Subject: NVMeoF: multipath stuck after bringing one ethernet port down
Date: Mon, 5 Jun 2017 17:07:55 +0200 [thread overview]
Message-ID: <20170605150755.GA29050@lst.de> (raw)
In-Reply-To: <d249a6d7-ae57-f9a1-e423-659cfa47c764@grimberg.me>
On Mon, Jun 05, 2017@11:53:58AM +0300, Sagi Grimberg wrote:
>> So this looks somewhat bogus to me, while the rest looks ok.
>
> The point here is that RECONNECTING is a ctrl state that has a
> potential to linger for a long time (unlike RESETTING or DELETING),
> so we don't want to trigger requeue right away.
>
> I'm open to other ideas. I just want to prevent triggering a redundant
> loop of queue_rq -> fail with BUSY -> queue_rq -> fail with BUSY ...
>
> Thoughts?
Let's get this patch in, then sort out a common stratefy for the
dev_loss_tmo for all drivers, as FC is already doing some work in
that area.
next prev parent reply other threads:[~2017-06-05 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 16:08 NVMeoF: multipath stuck after bringing one ethernet port down Alex Turin
2017-05-17 17:28 ` Sagi Grimberg
2017-05-18 5:52 ` shahar.salzman
2017-05-23 17:31 ` shahar.salzman
2017-05-25 11:06 ` shahar.salzman
2017-05-25 12:27 ` shahar.salzman
2017-05-25 13:08 ` shahar.salzman
2017-05-30 12:14 ` Sagi Grimberg
2017-05-30 12:11 ` Sagi Grimberg
2017-05-30 12:05 ` Sagi Grimberg
2017-05-30 13:37 ` Max Gurtovoy
2017-05-30 14:17 ` Sagi Grimberg
2017-06-05 7:11 ` shahar.salzman
2017-06-05 8:14 ` Sagi Grimberg
2017-06-05 8:40 ` Christoph Hellwig
2017-06-05 8:53 ` Sagi Grimberg
2017-06-05 15:07 ` Christoph Hellwig [this message]
2017-06-05 17:23 ` 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=20170605150755.GA29050@lst.de \
--to=hch@lst.de \
/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