linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sbates@raithlin.com (Stephen Bates)
Subject: [PATCH 0/1] nvme : Add sysfs entry for NVMe CMBs when appropriate
Date: Tue, 27 Sep 2016 16:15:12 -0600	[thread overview]
Message-ID: <1475014513-18083-1-git-send-email-sbates@raithlin.com> (raw)

We have had a few attempts at adding CMB properties and control to
sysfs [1][2]. This patch is based on Jon Derrick's [1] to some exent but
takes a much more conservative approach by only displaying CMB
properties and not attmpting to control them. Assuming this gets
accepted I do have a follow-on that adds more information to the cmb
attribute file.

Rather nicely we contain these changes solely to pci.c.

Applies to commit 1a6fe74dfd1b ("nvme: Pass pointers, not dma
addresses, to nvme_get/set_features()") in Jens' for-4.9/block branch.

Tested on both QEMU and on some real hardware I have access too that can
advertise and expose a CMB.

[1] http://www.spinics.net/lists/linux-block/msg01560.html
[2] http://www.spinics.net/lists/linux-rdma/msg38752.html

Stephen Bates (1):
  nvme : Add sysfs entry for NVMe CMBs when appropriate

 drivers/nvme/host/pci.c | 46 ++++++++++++++++++++++++++++++++++++----------
 1 file changed, 36 insertions(+), 10 deletions(-)

--
2.1.4

             reply	other threads:[~2016-09-27 22:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-27 22:15 Stephen Bates [this message]
2016-09-27 22:15 ` [PATCH 1/1] nvme : Add sysfs entry for NVMe CMBs when appropriate Stephen Bates
2016-09-27 23:17   ` Jon Derrick
2016-09-28  0:10     ` Stephen Bates
2016-10-05  8:22   ` Sagi Grimberg
2016-10-05 14:38     ` Stephen Bates
2016-10-05 16:50       ` Sagi Grimberg
2016-10-05 17:48         ` Stephen Bates
2016-10-05 18:20           ` J Freyensee

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=1475014513-18083-1-git-send-email-sbates@raithlin.com \
    --to=sbates@raithlin.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).