All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH 1/2] nvme-cli: add minimal ana-log page support
Date: Wed, 25 Jul 2018 08:48:48 -0600	[thread overview]
Message-ID: <20180725144848.GC14596@localhost.localdomain> (raw)
In-Reply-To: <20180725045352.GA10905@lst.de>

On Wed, Jul 25, 2018@06:53:52AM +0200, Christoph Hellwig wrote:
> On Tue, Jul 24, 2018@05:13:15PM -0700, Chaitanya Kulkarni wrote:
> > This patch adds a new command to retrieve the ANA Log page.
> > We update identify ctrl/ns data structure to support this command.
> > We also add ana based error codes and different identifiers to the
> > linux/nvme.h header file in order to support this command.
> 
> One thing I am a little concerned about here is that reading the
> ANA log page may clear the ANA AEN.  This actually is the same for
> other log pages that clear AENs, but for ANA the effects are much
> worse.
> 
> Keith, wat do you think of always setting the RAE bit for log pages
> associated with AENs?  The only real issue I can see is that the
> bit is only defined for NVMe 1.3+ so we'd need to figure out the
> version somehow.  Maybe with a new ioctl so that we don't have
> to send an identify every time.

Adding the RAE option for user space tooling is a good idea. Defaulting to
on should be safe too (will confirm on older drives), but does re-arming
the AEN really create a problem for ANA? I thought the log page problem
was when reading a page changes the result of the next read, but that
only applies to very few logs.

  parent reply	other threads:[~2018-07-25 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-25  0:13 [PATCH 1/2] nvme-cli: add minimal ana-log page support Chaitanya Kulkarni
2018-07-25  0:13 ` [PATCH 2/2] nvme-cli add ana-log documentation Chaitanya Kulkarni
2018-07-25  4:53 ` [PATCH 1/2] nvme-cli: add minimal ana-log page support Christoph Hellwig
2018-07-25  6:43   ` Chaitanya Kulkarni
2018-07-25 14:48   ` Keith Busch [this message]
2018-07-26  9:24     ` Christoph Hellwig
2018-07-26 14:29       ` Keith Busch

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=20180725144848.GC14596@localhost.localdomain \
    --to=keith.busch@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.