From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH] nvme-rdma: Don't fail the controller if only part of the queues fail to connect
Date: Thu, 8 Nov 2018 16:00:39 -0800 [thread overview]
Message-ID: <16e16abf-a1cc-a2f7-f5bc-4158236bffe4@grimberg.me> (raw)
In-Reply-To: <20181108083751.GA3465@lst.de>
> No, I'm arguing that adding this just in case code which doesn't
> have a good way to actually catch a typical bug is not very useful.
Regardless of the specific error code, the question is do we want
to be able to still continue degraded operation if we happen to fail
queue allocation. A different error could be that we failed to connect
because the target is overloaded..
next prev parent reply other threads:[~2018-11-09 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-04 16:37 [PATCH] nvme-rdma: Don't fail the controller if only part of the queues fail to connect Israel Rukshin
2018-11-04 17:09 ` [Suspected-Phishing][PATCH] " Max Gurtovoy
2018-11-05 19:34 ` [PATCH] " James Smart
2018-11-06 11:10 ` Max Gurtovoy
2018-11-07 9:07 ` Christoph Hellwig
2018-11-07 18:31 ` Sagi Grimberg
2018-11-08 8:20 ` Max Gurtovoy
2018-11-08 8:37 ` Christoph Hellwig
2018-11-08 14:46 ` Max Gurtovoy
2018-11-08 14:58 ` Christoph Hellwig
2018-11-09 0:00 ` Sagi Grimberg [this message]
2018-11-09 18:55 ` James Smart
2018-11-09 21:52 ` 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=16e16abf-a1cc-a2f7-f5bc-4158236bffe4@grimberg.me \
--to=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;
as well as URLs for NNTP newsgroup(s).