linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wim Van Sebroeck <wim@iguana.be>
To: anish kumar <anish198519851985@gmail.com>
Cc: linux@roeck-us.net, linux-watchdog@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [RFC]Watchdog:core: constant pinging until userspace timesout when delay very less
Date: Thu, 27 Jun 2013 21:31:38 +0200	[thread overview]
Message-ID: <20130627193138.GB30433@spo001.leaseweb.com> (raw)
In-Reply-To: <1370167987-14252-1-git-send-email-anish198519851985@gmail.com>

Hi Anish,

> Certain watchdog drivers use a timer to keep kicking the watchdog at
> a rate of 0.5s (HZ/2) untill userspace times out.They do this as
> we can't guarantee that watchdog will be pinged fast enough
> for all system loads, especially if timeout is configured for
> less than or equal to 1 second(basically small values).
> 
> As suggested by Wim Van Sebroeck & Guenter Roeck we should
> add this functionality of individual watchdog drivers in the core
> watchdog core.

Have you considered the effect this change has on all watchdog drivers
that don't need a timer?

Kind regards,
Wim.


  parent reply	other threads:[~2013-06-27 19:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-02 10:13 [PATCH] [RFC]Watchdog:core: constant pinging until userspace timesout when delay very less anish kumar
2013-06-02 10:26 ` anish singh
2013-06-03 14:38   ` anish singh
2013-06-03 15:27 ` Guenter Roeck
2013-06-03 16:53   ` anish singh
2013-06-03 22:25     ` Guenter Roeck
2013-06-04  3:09       ` anish singh
2013-06-05  3:09         ` anish singh
2013-06-06  3:00           ` anish singh
2013-06-06  4:41             ` Guenter Roeck
2013-06-08 13:14               ` anish singh
2013-06-27 19:31 ` Wim Van Sebroeck [this message]
2013-06-28  3:31   ` anish singh

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=20130627193138.GB30433@spo001.leaseweb.com \
    --to=wim@iguana.be \
    --cc=anish198519851985@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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).