All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: Lijun Pan <lijunpan2000@gmail.com>
Cc: Lijun Pan <Lijun.Pan@dell.com>,
	Stuart Hayes <Stuart.Hayes@dell.com>,
	"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>
Subject: Re: [PATCH v2] libndctl: add support for the MSFT family of DSM functions
Date: Wed, 29 Mar 2017 11:13:02 -0700	[thread overview]
Message-ID: <CAPcyv4g623k8L11ong4yccSmFFPmtKyieFSdKS0n3KGqGkYRYw@mail.gmail.com> (raw)
In-Reply-To: <20170326201753.1522-1-lijunpan2000@gmail.com>

On Sun, Mar 26, 2017 at 1:17 PM, Lijun Pan <lijunpan2000@gmail.com> wrote:
> From: Lijun Pan <Lijun.Pan@dell.com>
>
> This patch retrieves the health data from NVDIMM-N via
> the MSFT _DSM function[1], following JESD245A[2] standards.
> Now 'ndctl list --dimms --health --idle' could work
> on MSFT type NVDIMM-N, but limited to health_state,
> temperature_celsius, and life_used_percentage.

Looks good, can you add sample output of:

    ndctl list --dimms --health --idle

...so users know what to expect. With that change and addressing
Linda's comment about the temperature multiplier I think we're good to
go.

Also, if you want to add Microsoft-only health attributes we'll need
to add new "valid" flags beyond the current ND_SMART_*_VALID set. If
this goes beyond the current 32 "valid" flags that that
ndctl_cmd_smart_get_flags() returns we might need a new
ndctl_cmd_smart_get_flags2() call that returns an arbitrary bitmap of
valid flags.

We'd also need to move those definitions to an ndctl local header.
Currently where they are defined now in ndctl.h is owned by the
kernel. We can cross this bridge later in a follow-on patch.
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  parent reply	other threads:[~2017-03-29 18:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 20:17 [PATCH v2] libndctl: add support for the MSFT family of DSM functions Lijun Pan
2017-03-28 22:01 ` Linda Knippers
2017-03-28 23:14   ` Lijun.Pan
2017-03-28 23:37     ` Linda Knippers
2017-03-29 15:08   ` Lijun.Pan
2017-03-29 15:29     ` Linda Knippers
2017-03-29 18:13 ` Dan Williams [this message]
2017-03-29 21:41   ` Lijun.Pan
2017-03-29 22:26     ` Elliott, Robert (Persistent Memory)
2017-03-29 23:35       ` Lijun.Pan
2017-03-30 15:20       ` Linda Knippers
2017-03-30 15:19     ` Linda Knippers

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=CAPcyv4g623k8L11ong4yccSmFFPmtKyieFSdKS0n3KGqGkYRYw@mail.gmail.com \
    --to=dan.j.williams@intel.com \
    --cc=Lijun.Pan@dell.com \
    --cc=Stuart.Hayes@dell.com \
    --cc=lijunpan2000@gmail.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 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.