From: hare@suse.com (Hannes Reinecke)
Subject: [PATCH] nvme: schedule requeue whenever a LIVE state is entered
Date: Fri, 22 Mar 2019 07:55:55 +0100 [thread overview]
Message-ID: <0ccee425-93bb-ad04-5b20-f8a792f1aafa@suse.com> (raw)
In-Reply-To: <da58a1e4-14cd-2587-6350-dccabb6632f1@grimberg.me>
On 3/21/19 10:26 PM, Sagi Grimberg wrote:
>
>> When undergoing state transitions I/O might be requeued, hence
>> we always have to schedule requeue_work whenever the nvme device
>> is live, independent on whether the old state was live or not.
>
> Any reason why not simply update from live to live?
>
?
I somewhat fail to parse the answer.
Care to elaborate?
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare at suse.com +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: F. Imend?rffer, J. Smithard, D. Upmanyu, G. Norton
HRB 21284 (AG N?rnberg)
next prev parent reply other threads:[~2019-03-22 6:55 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 [this message]
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
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=0ccee425-93bb-ad04-5b20-f8a792f1aafa@suse.com \
--to=hare@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox