From: james_p_freyensee@linux.intel.com (J Freyensee)
Subject: [PATCH 2/3] fine tune the nvme-discover manpage
Date: Thu, 13 Oct 2016 09:43:17 -0700 [thread overview]
Message-ID: <1476376997.6246.3.camel@linux.intel.com> (raw)
In-Reply-To: <20161013102632.GA14543@lst.de>
On Thu, 2016-10-13@12:26 +0200, Christoph Hellwig wrote:
> On Wed, Oct 12, 2016@10:18:05AM -0700, J Freyensee wrote:
> >
> > >
> > > -nvme-discover - Send Get Log Page request to Discovery
> > > Controller.
> > > +nvme-discover - Send Discovery requests to Fabrics Discovery
> > > Controllers.
> >
> > I preferred mentioning "Get Log Page" because that is really what
> > is
> > happening and reflects the NVMe specification, which I was aiming
> > to
> > push the envelope a bit and help educate and accelerate the
> > learning
> > curve for people new to these features (map more accurately what is
> > being described here to the NVMe specification(s).
>
> While Get Log Page is technicaly correct I don't really think it
> serves the user much - it's the way the discovery is implemented,
> the important part is that we perform discovery.
I think it does serve the user, it educates the user a bit faster on
the NVMe Specification and what is really happening without spending
the time sorting through the spec, important for things like debugging
and diagnosis if something wonky happens.
next prev parent reply other threads:[~2016-10-13 16:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 8:45 nvme-cli documentation updates Christoph Hellwig
2016-10-12 8:45 ` [PATCH 1/3] consolidate reporting bugs information Christoph Hellwig
2016-10-12 17:13 ` J Freyensee
2016-10-12 8:45 ` [PATCH 2/3] fine tune the nvme-discover manpage Christoph Hellwig
2016-10-12 17:18 ` J Freyensee
2016-10-13 10:26 ` Christoph Hellwig
2016-10-13 16:43 ` J Freyensee [this message]
2016-10-12 8:45 ` [PATCH 3/3] add documentation for the connect-all command Christoph Hellwig
2016-10-12 17:21 ` J Freyensee
2016-10-13 10:27 ` Christoph Hellwig
2016-10-12 19:23 ` nvme-cli documentation updates 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=1476376997.6246.3.camel@linux.intel.com \
--to=james_p_freyensee@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.