Linux-NVDIMM Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Knippers <linda.knippers@hpe.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: 'ndctl list' question
Date: Mon, 17 Jul 2017 13:04:31 -0400	[thread overview]
Message-ID: <596CEE1F.3060803@hpe.com> (raw)

Hi Dan,

I have 8 NVDIMMs in my system and I have them configured in various ways.
When I run 'ndctl list', I get a nice simple summary of all of my devices.
What's missing though is the "chardev" information for my dax devices.

I do see that I can get it, and more, if I run 'ndctl list -X' but that
only gives me information about dax namespaces. I can also get it if I run
'daxctl list', but without any other useful information.  You can see all
the sample output below.

Is there a reason we can't have "chardev" in the output of 'ndctl list'
so that all the basic information is in one place?  I'm happy to do a
patch but since this has changed a bit (and I think the information
used to be there?), I thought I'd ask if there's a reason you omitted it.

Thanks,

-- ljk


$ ndctl list
[
  {
    "dev":"namespace1.0",
    "mode":"memory",
    "size":"8.00 GiB",
    "uuid":"322314b3-283b-40d9-a2fa-be73ff34b373",
    "blockdev":"pmem1",
    "numa_node":0
  },
  {
    "dev":"namespace3.0",
    "mode":"sector",
    "size":"7.99 GiB",
    "uuid":"df9992df-8d90-4017-be65-8166ab1fbe7e",
    "sector_size":4096,
    "blockdev":"pmem3s",
    "numa_node":0
  },
  {
    "dev":"namespace5.0",
    "mode":"raw",
    "size":"8.00 GiB",
    "blockdev":"pmem5",
    "numa_node":1
  },
  {
    "dev":"namespace7.0",
    "mode":"dax",
    "size":"7.87 GiB",
    "uuid":"c57b18aa-0c6a-4775-aa3e-e25f2a7c0c2f",
    "numa_node":1
  },
  {
    "dev":"namespace0.0",
    "mode":"memory",
    "size":"7.87 GiB",
    "uuid":"e5405210-373e-4604-94a2-4e42c73ecac0",
    "blockdev":"pmem0",
    "numa_node":0
  },
  {
    "dev":"namespace2.0",
    "mode":"memory",
    "size":"7.87 GiB",
    "uuid":"cd79114e-5f47-4b38-9511-fd130e0a34f4",
    "blockdev":"pmem2",
    "numa_node":0
  },
  {
    "dev":"namespace4.0",
    "mode":"dax",
    "size":"7.87 GiB",
    "uuid":"0c6c079b-57bb-48dd-9959-d2156f2f17ba",
    "numa_node":1
  },
  {
    "dev":"namespace6.0",
    "mode":"raw",
    "size":"8.00 GiB",
    "blockdev":"pmem6",
    "numa_node":1
  }
]

$ daxctl list
[
  {
    "chardev":"dax7.0",
    "size":"7.87 GiB"
  },
  {
    "chardev":"dax4.0",
    "size":"7.87 GiB"
  }
]

$ ndctl list -X
[
  {
    "dev":"namespace7.0",
    "mode":"dax",
    "size":"7.87 GiB",
    "uuid":"c57b18aa-0c6a-4775-aa3e-e25f2a7c0c2f",
    "daxregion":{
      "id":7,
      "size":"7.87 GiB",
      "align":4096,
      "devices":[
        {
          "chardev":"dax7.0",
          "size":"7.87 GiB"
        }
      ]
    },
    "numa_node":1
  },
  {
    "dev":"namespace4.0",
    "mode":"dax",
    "size":"7.87 GiB",
    "uuid":"0c6c079b-57bb-48dd-9959-d2156f2f17ba",
    "daxregion":{
      "id":4,
      "size":"7.87 GiB",
      "align":4096,
      "devices":[
        {
          "chardev":"dax4.0",
          "size":"7.87 GiB"
        }
      ]
    },
    "numa_node":1
  }
]
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

                 reply	other threads:[~2017-07-17 17:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=596CEE1F.3060803@hpe.com \
    --to=linda.knippers@hpe.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    /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