linux-nvdimm.lists.01.org archive mirror
 help / color / mirror / Atom feed
From: Vishal Verma <vishal.l.verma@intel.com>
To: Vaibhav Jain <vaibhav@linux.ibm.com>, linux-nvdimm@lists.01.org
Cc: "Aneesh Kumar K . V" <aneesh.kumar@linux.ibm.com>
Subject: Re: [ndctl RESEND PATCH v2] monitor: Add epoll timeout for forcing a full dimm health check
Date: Tue, 21 Jul 2020 23:29:08 -0600	[thread overview]
Message-ID: <e5887e208e958938f134591a53d02a7402d8b8a4.camel@intel.com> (raw)
In-Reply-To: <20200722052455.339169-1-vaibhav@linux.ibm.com>

On Wed, 2020-07-22 at 10:54 +0530, Vaibhav Jain wrote:
> This patch adds a new command argument to the 'monitor' command namely
> '--poll' that triggers a call to notify_dimm_event() at regular
> intervals forcing a periodic check of status/events for the nvdimm
> objects i.e. bus, dimms, regions or namespaces.
> 
> This behavior is useful for dimms that do not support event notifications
> in case the health status of an nvdimm changes. This is especially
> true in case of PAPR-SCM nvdimms as the PHYP hypervisor doesn't provide
> any notifications to the guest kernel on a change in nvdimm health
> status. In such case periodic polling of the is the only way to track
> the health of a nvdimm.
> 
> The patch updates monitor_event() adding a timeout value to
> epoll_wait() call. Also to prevent the possibility of a single dimm
> generating enough events thereby preventing check for status of other
> nvdimms objects, a 'fullpoll_ts' time-stamp is added to keep track of
> when full check of all nvdimms objects happened. If after epoll_wait()
> returns 'fullpoll_ts' time-stamp indicates last a full status check
> for nvdimm objects happened beyond 'poll-interval' seconds then a full
> status check is enforced.
> 
> Cc: QI Fuli <qi.fuli@jp.fujitsu.com>
> Cc: Dan Williams <dan.j.williams@intel.com>
> Cc: Vishal Verma <vishal.l.verma@intel.com>
> Signed-off-by: Vaibhav Jain <vaibhav@linux.ibm.com>
> ---
> Changelog:
> 
> Resend
> * None
> 
Hi Vaibhav,

I do have this queued up in my staging branch, I've just yet to push it out :)

Thanks for the ping!
-Vishal


_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

      reply	other threads:[~2020-07-22  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-22  5:24 [ndctl RESEND PATCH v2] monitor: Add epoll timeout for forcing a full dimm health check Vaibhav Jain
2020-07-22  5:29 ` Vishal Verma [this message]

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=e5887e208e958938f134591a53d02a7402d8b8a4.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=aneesh.kumar@linux.ibm.com \
    --cc=linux-nvdimm@lists.01.org \
    --cc=vaibhav@linux.ibm.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).