From: daniel.verkamp@intel.com (Daniel Verkamp)
Subject: [PATCH 06/12] nvmet: implement the changed namespaces log
Date: Wed, 30 May 2018 10:33:49 -0700 [thread overview]
Message-ID: <0c4cc53d-1c28-0bf5-d454-df6c9ef9335b@intel.com> (raw)
In-Reply-To: <20180530164600.26856-7-hch@lst.de>
On 05/30/2018 09:45 AM, Christoph Hellwig wrote:
> Just keep a per-controller buffer of changed namespaces and copy it out
> in the get log page implementation.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
> ---
[...]
> +static void nvmet_add_to_changed_ns_log(struct nvmet_ctrl *ctrl, __le32 nsid)
> +{
> + mutex_lock(&ctrl->lock);
> + if (ctrl->nr_changed_ns < NVME_MAX_CHANGED_NAMESPACES) {
Minor nitpick here: if ctrlr->nr_changed_ns is exactly
NVME_MAX_CHANGED_NAMESPACES and the new nsid is already in the list,
this will skip down to the 0xffffffff case below, even though it could
have just left the list as-is.
I don't know if this is a problem in practice; reporting 0xffffffff is
probably always safe, since the host will presumably treat that as
"rescan everything".
> + u32 i;
> +
> + for (i = 0; i < ctrl->nr_changed_ns; i++)
> + if (ctrl->changed_ns_list[i] == nsid)
> + goto out_unlock;
> + ctrl->changed_ns_list[ctrl->nr_changed_ns++] = nsid;
> + } else if (ctrl->nr_changed_ns == NVME_MAX_CHANGED_NAMESPACES) {
> + ctrl->changed_ns_list[0] = cpu_to_le32(0xffffffff);
> + ctrl->nr_changed_ns = U32_MAX;
> + }
> +out_unlock:
> + mutex_unlock(&ctrl->lock);
> +}
Thanks,
-- Daniel
next prev parent reply other threads:[~2018-05-30 17:33 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 16:45 nvme/nvmet AEN and log page fixups v2 Christoph Hellwig
2018-05-30 16:45 ` [PATCH 01/12] nvme.h: untangle AEN notice definitions Christoph Hellwig
2018-05-30 21:21 ` Sagi Grimberg
2018-06-04 6:13 ` Hannes Reinecke
2018-06-04 6:13 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 02/12] nvme.h: add the changed namespace list log Christoph Hellwig
2018-05-30 21:22 ` Sagi Grimberg
2018-06-04 6:13 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 03/12] nvme.h: add AER configuration symbols Christoph Hellwig
2018-05-30 21:23 ` Sagi Grimberg
2018-05-30 16:45 ` [PATCH 04/12] nvmet: add a new nvmet_zero_sgl helper Christoph Hellwig
2018-05-30 21:24 ` Sagi Grimberg
2018-06-04 6:14 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 05/12] nvmet: split log page implementation Christoph Hellwig
2018-05-30 21:25 ` Sagi Grimberg
2018-06-04 6:14 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 06/12] nvmet: implement the changed namespaces log Christoph Hellwig
2018-05-30 17:33 ` Daniel Verkamp [this message]
2018-05-31 16:25 ` Christoph Hellwig
2018-05-31 16:36 ` Daniel Verkamp
2018-05-30 21:28 ` Sagi Grimberg
2018-06-04 6:15 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 07/12] nvmet: Add AEN configuration support Christoph Hellwig
2018-05-30 21:30 ` Sagi Grimberg
2018-05-30 16:45 ` [PATCH 08/12] nvmet: mask pending AERs Christoph Hellwig
2018-05-30 21:31 ` Sagi Grimberg
2018-06-04 6:15 ` Hannes Reinecke
2018-06-12 15:41 ` Israel Rukshin
2018-06-13 7:42 ` Christoph Hellwig
2018-06-13 8:23 ` Max Gurtovoy
2018-06-13 11:26 ` Christoph Hellwig
2018-06-19 14:03 ` Sagi Grimberg
2018-05-30 16:45 ` [PATCH 09/12] nvme: submit AEN event configuration on startup Christoph Hellwig
2018-05-30 21:31 ` Sagi Grimberg
2018-05-30 16:45 ` [PATCH 10/12] nvme: mark nvme_queue_scan static Christoph Hellwig
2018-05-30 21:31 ` Sagi Grimberg
2018-06-04 6:16 ` Hannes Reinecke
2018-05-30 16:45 ` [PATCH 11/12] nvme: use the changed namespaces list log to clear ns data changed AENs Christoph Hellwig
2018-05-30 21:34 ` Sagi Grimberg
2018-06-04 6:16 ` Hannes Reinecke
2018-05-30 16:46 ` [PATCH 12/12] nvme: limit warnings from nvme_identify_ns Christoph Hellwig
2018-05-30 21:35 ` Sagi Grimberg
2018-06-04 6:17 ` 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=0c4cc53d-1c28-0bf5-d454-df6c9ef9335b@intel.com \
--to=daniel.verkamp@intel.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;
as well as URLs for NNTP newsgroup(s).