From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH] nvme: schedule requeue whenever a LIVE state is entered
Date: Wed, 27 Mar 2019 09:37:24 +0100 [thread overview]
Message-ID: <20190327083724.GR20525@lst.de> (raw)
In-Reply-To: <ec71c2a4-d3e1-36ad-b7bc-0e8e6e394a5d@grimberg.me>
On Mon, Mar 25, 2019@08:55:47AM -0700, Sagi Grimberg wrote:
>
>> That's what we tried initially (cf thread "[PATCH] nvme-multipath: relax
>> ANA state check"), but got rejected by Christoph.
>
> IIRC Christoph was asking why was requests being requeued when moving
> from live -> live, and I think you answered that in your patch
> description..
Exactltly. Asking to please explain WTF is happening is not rejecting,
it is asking for more information to actually understand the issue.
So the patch from Georg with a changelog and comment in the code based
on yours seems like what we need.
next prev parent reply other threads:[~2019-03-27 8:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 14:10 [PATCH] nvme: schedule requeue whenever a LIVE state is entered Hannes Reinecke
2019-03-21 21:26 ` Sagi Grimberg
2019-03-22 6:55 ` Hannes Reinecke
2019-03-22 18:57 ` Sagi Grimberg
2019-03-22 21:14 ` Hannes Reinecke
2019-03-25 15:55 ` Sagi Grimberg
2019-03-27 8:37 ` Christoph Hellwig [this message]
2019-03-27 8:44 ` Hannes Reinecke
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=20190327083724.GR20525@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