From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/4] nvmet: make ANATT configurable
Date: Thu, 7 Jun 2018 14:06:12 +0200 [thread overview]
Message-ID: <20180607120612.GA11938@lst.de> (raw)
In-Reply-To: <20180607073556.39050-2-hare@suse.de>
Needs a description. Especially to explain why you want it
per-port. In the end the transition timeout is something determined
by the failover backend, which in no way maps to a port. In fact
it doesn't map to anything, which is why I would suggest to just
make it global. This still won't cover the case of using different
backed storage types with different failover characteristics, but
at least it ?sn't too confusing.
> + ret = kstrtou8(page, 0, &ana_tt);
> + if (ret || ana_tt == 0)
> + return -EINVAL;
Please propagate the actual error returned by kstrtou8.
> +
> + if (port->enabled) {
> + pr_err("Cannot modify ANA transition timeout while enabled\n");
> + return -EACCES;
> + }
> + down_write(&nvmet_config_sem);
> + port->anatt = ana_tt;
> + up_write(&nvmet_config_sem);
The enabled check needs to be under nvmet_config_sem to be race free.
next prev parent reply other threads:[~2018-06-07 12:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 7:35 [PATCH 0/4] nvme: ANATT handling Hannes Reinecke
2018-06-07 7:35 ` [PATCH 1/4] nvmet: make ANATT configurable Hannes Reinecke
2018-06-07 12:06 ` Christoph Hellwig [this message]
2018-06-07 12:42 ` Hannes Reinecke
2018-06-07 13:03 ` Sagi Grimberg
2018-06-07 7:35 ` [PATCH 2/4] nvmet: ANA transition timeout handling Hannes Reinecke
2018-06-07 12:07 ` Christoph Hellwig
2018-06-07 13:31 ` Hannes Reinecke
2018-06-07 13:41 ` Christoph Hellwig
2018-06-07 13:12 ` Sagi Grimberg
2018-06-07 7:35 ` [PATCH 3/4] nvme: " Hannes Reinecke
2018-06-07 12:09 ` Christoph Hellwig
2018-06-07 12:52 ` Hannes Reinecke
2018-06-07 13:11 ` Christoph Hellwig
2018-06-07 13:16 ` Sagi Grimberg
2018-06-07 13:26 ` Christoph Hellwig
2018-06-07 7:35 ` [PATCH 4/4] nvme: start ANATT timer on out-of-order state changes Hannes Reinecke
2018-06-07 12:11 ` Christoph Hellwig
2018-06-07 12:37 ` Hannes Reinecke
2018-06-07 13:10 ` Christoph Hellwig
2018-06-07 13:20 ` Hannes Reinecke
2018-06-07 13:46 ` Christoph Hellwig
2018-06-07 14:01 ` Hannes Reinecke
2018-06-07 14:22 ` Christoph Hellwig
2018-06-07 15:20 ` Sagi Grimberg
2018-06-07 13:20 ` 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=20180607120612.GA11938@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