From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 05/10] nvme: add ANA support
Date: Thu, 7 Jun 2018 15:05:59 +0200 [thread overview]
Message-ID: <20180607130559.GA13101@lst.de> (raw)
In-Reply-To: <56eca832-5b3c-9ba8-c953-924f3fb7609f@grimberg.me>
On Thu, Jun 07, 2018@03:49:20PM +0300, Sagi Grimberg wrote:
>> + * XXX: We should verify the controller doesn't die on during
>> + * the transition. But that means we per-group timeout from
>> + * when we first hit the change state, so this won't be
>> + * entirely trivial..
>
> something is wrong with the sentence I think "that means we per-group
> timeout from when..."
>
> Not sure what you are trying to say.
Reading it again it really looks gibberish.. Hopefully we don't
need the comment any more for next time as Hannes is working on
actually implementing the ANATT timer.
>> +static void nvme_ana_work(struct work_struct *work)
>> +{
>> + struct nvme_ctrl *ctrl = container_of(work, struct nvme_ctrl, ana_work);
>> +
>> + nvme_process_ana_log(ctrl, false);
>> + nvme_kick_requeue_lists(ctrl);
>
> Won't it make sense to kick the requeue list only for namespaces that
> are involved in ana state change? Won't attempting this on all
> the namespaces might result in retry count increment for namespaces
> that are inaccessible? those retries are finite by nvme_max_retries...
It makes sense, except that we it would take a lot of effort to figure
out what namespace actually changed due to the group indirection.
What we can do more easily is to only kick it off again on live
namespaces, so I'll look into that.
next prev parent reply other threads:[~2018-06-07 13:05 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 14:33 draft ANA support v3 Christoph Hellwig
2018-06-06 14:33 ` [PATCH 01/10] nvme.h: add support for the log specific field Christoph Hellwig
2018-06-07 7:27 ` Johannes Thumshirn
2018-06-07 7:58 ` Hannes Reinecke
2018-06-07 12:34 ` Sagi Grimberg
2018-06-06 14:33 ` [PATCH 02/10] nvme.h: add ANA definitions Christoph Hellwig
2018-06-07 7:59 ` Hannes Reinecke
2018-06-07 8:30 ` Johannes Thumshirn
2018-06-07 12:35 ` Sagi Grimberg
2018-06-06 14:33 ` [PATCH 03/10] nvme: simplify the API for getting log pages Christoph Hellwig
2018-06-07 7:39 ` Johannes Thumshirn
2018-06-07 7:59 ` Hannes Reinecke
2018-06-07 12:35 ` Sagi Grimberg
2018-06-06 14:33 ` [PATCH 04/10] nvme: remove nvme_req_needs_failover Christoph Hellwig
2018-06-07 7:40 ` Johannes Thumshirn
2018-06-07 8:01 ` Hannes Reinecke
2018-06-07 11:57 ` Christoph Hellwig
2018-06-07 12:36 ` Sagi Grimberg
2018-06-06 14:33 ` [PATCH 05/10] nvme: add ANA support Christoph Hellwig
2018-06-07 8:01 ` Hannes Reinecke
2018-06-07 12:49 ` Sagi Grimberg
2018-06-07 13:05 ` Christoph Hellwig [this message]
2018-06-07 13:55 ` Christoph Hellwig
2018-06-06 14:33 ` [PATCH 06/10] nvme: don't set gendisks live that don't have an I/O capable path Christoph Hellwig
2018-06-06 14:33 ` [PATCH 07/10] nvmet: track and limit the number of namespaces per subsystem Christoph Hellwig
2018-06-07 7:54 ` Johannes Thumshirn
2018-06-07 8:02 ` Hannes Reinecke
2018-06-06 14:33 ` [PATCH 08/10] nvmet: add minimal ANA support Christoph Hellwig
2018-06-07 8:03 ` Hannes Reinecke
2018-06-07 12:52 ` Sagi Grimberg
2018-06-06 14:33 ` [PATCH 09/10] nvmet: support configuring ANA groups Christoph Hellwig
2018-06-07 8:09 ` Hannes Reinecke
2018-06-07 12:02 ` Christoph Hellwig
2018-06-07 12:58 ` Sagi Grimberg
2018-06-07 13:08 ` Christoph Hellwig
2018-06-06 14:33 ` [PATCH 10/10] host fold Christoph Hellwig
2018-06-06 14:46 ` Christoph Hellwig
2018-06-06 15:18 ` Hannes Reinecke
2018-06-07 12:34 ` draft ANA support v3 Sagi Grimberg
2018-06-07 13:06 ` Christoph Hellwig
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=20180607130559.GA13101@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