All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
	"qi.fuli@jp.fujitsu.com" <qi.fuli@jp.fujitsu.com>
Subject: Re: [RFC PATCH v3 0/5] ndctl: monitor: monitor the smart events of
Date: Fri, 9 Feb 2018 18:06:28 +0000	[thread overview]
Message-ID: <1518199586.8128.55.camel@intel.com> (raw)
In-Reply-To: <20180209080225.5137-1-qi.fuli@jp.fujitsu.com>


On Fri, 2018-02-09 at 17:02 +0900, QI Fuli wrote:
> This is a patch set of ndctl monitor, a tiny daemon to monitor the
> smart
> events of nvdimm dimms. When a smart event fires, monitor will output
> the notification which including dimm health status to syslog or a
> special file according to users' configuration. The output
> notification
> follows json format and can be consumed by log collectors like
> Fluentd.
> 
> Currently, I implemeted the following four commands to control
> monitor daemon.
> $ndctl create-monitor
> $ndctl list-monitor
> $ndctl show-monitor
> $ndclt destroy-monitor
> 
> I will appreciate if you could give some comments.
> 
> Change log since v2:
>  - Changing the interface of daemon to the ndctl command line
>  - Changing the name of daemon form "nvdimmd" to "monitor"
>  - Removing the config file, unit_file, nvdimmd dir
>  - Removing nvdimmd_test program
>  - Adding ndctl/monitor.c
> 
> Change log since v1:
>  - Adding a config file(/etc/nvdimmd/nvdimmd.conf)
>  - Using struct log_ctx instead of syslog()
>     - Using log_syslog() to save the notify messages to syslog
>     - Using log_file() to save the notify messages to special file
>  - Adding LOG_NOTICE level to log_priority
>  - Using automake instead of Makefile
>  - Adding a new util file(nvdimmd/util.c) including helper functions
>    needed for nvdimm daemon
>  - Adding nvdimmd_test program
> 
> QI Fuli (5):
>   ndctl: monitor: add LOG_NOTICE level to log_priority
>   ndctl: monitor: add ndclt create-monitor command
>   ndctl: monitor: add ndclt list-monitor command
>   ndctl: monitor: add ndclt show-monitor command
>   ndctl: monitor: add ndclt destroy-monitor command
                        ^
I haven't had a chance to look at the rest of the series, but spotted a
quick typo - this is in the subject line of each commit as well:
s/ndclt/ndctl/

> 
>  builtin.h         |   4 +
>  configure.ac      |   3 +
>  ndctl/Makefile.am |   3 +-
>  ndctl/monitor.c   | 463
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>  ndctl/ndctl.c     |   4 +
>  util/log.c        |   2 +
>  util/log.h        |   3 +
>  7 files changed, 481 insertions(+), 1 deletion(-)
>  create mode 100644 ndctl/monitor.c
> 
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm

  parent reply	other threads:[~2018-02-09 18:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-09  8:02 [RFC PATCH v3 0/5] ndctl: monitor: monitor the smart events of QI Fuli
2018-02-09  8:02 ` [RFC PATCH v3 1/5] ndctl: nvdimmd: add LOG_NOTICE level to QI Fuli
2018-02-11 20:18   ` Dan Williams
2018-02-11 20:20     ` Dan Williams
2018-02-09  8:02 ` [RFC PATCH v3 2/5] ndctl: monitor: add ndctl create-monitor command QI Fuli
2018-02-11 20:48   ` Dan Williams
2018-02-13  0:54     ` Verma, Vishal L
2018-02-15  5:51       ` Qi, Fuli
2018-02-17  1:23         ` Dan Williams
2018-02-13  9:58     ` Yasunori Goto
2018-02-13 10:12       ` Yasunori Goto
2018-02-17  1:00         ` Dan Williams
2018-02-19  2:36           ` Yasunori Goto
2018-02-17  0:54       ` Dan Williams
2018-02-09  8:02 ` [RFC PATCH v3 3/5] ndctl: monitor: add ndclt list-monitor command QI Fuli
2018-02-09  8:02 ` [RFC PATCH v3 4/5] ndctl: monitor: add ndclt show-monitor command QI Fuli
2018-02-09  8:02 ` [RfC PATCH v3 5/5] ndctl: monitor: add ndclt destroy-monitor command QI Fuli
2018-02-09 18:06 ` Verma, Vishal L [this message]
2018-02-13  1:51   ` [RFC PATCH v3 0/5] ndctl: monitor: monitor the smart events of Qi, Fuli
2018-02-10  4:06 ` Dan Williams
2018-02-13  1:54   ` Qi, Fuli

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=1518199586.8128.55.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=qi.fuli@jp.fujitsu.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.