From: Alexander Stein <alexander.stein@systec-electronic.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-watchdog@vger.kernel.org
Subject: Re: watchdog timeout in sub-seconds?
Date: Tue, 14 Apr 2015 10:15:44 +0200 [thread overview]
Message-ID: <4398543.5EAQg64u7T@ws-stein> (raw)
In-Reply-To: <552BCA3E.5010305@roeck-us.net>
On Monday 13 April 2015 06:53:02, Guenter Roeck wrote:
> On 04/13/2015 06:33 AM, Alexander Stein wrote:
> > Hi,
> >
> > is there a specific reason that the timeout in the linux watchdog drivers is
> > only provided in seconds resolution? What about timeouts in ms area/precision?
> >
>
> The question would probably be why not. On a loaded system, sub-second
> watchdog timeouts are quite unreasonable.
>
> In other words, you would have to provide a very good argument for
> sub-second timeouts if you see the need for it. That some hardware
> may require it is not really an argument here - this is all about
> user space - kernel interface, not about limitations of specific
> hardware.
Well, after discussing this a bit why the hardware watchdog has ms resolution support it turns out this is mainly for safety related devices which seem to require such short timeouts. It doesn't seem to be required on this linux based board though. So this issue has been cleared itself.
Best regards,
Alexander
--
Dipl.-Inf. Alexander Stein
SYS TEC electronic GmbH
Am Windrad 2
08468 Heinsdorfergrund
Tel.: 03765 38600-1156
Fax: 03765 38600-4100
Email: alexander.stein@systec-electronic.com
Website: www.systec-electronic.com
Managing Director: Dipl.-Phys. Siegmar Schmidt
Commercial registry: Amtsgericht Chemnitz, HRB 28082
prev parent reply other threads:[~2015-04-14 8:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 13:33 watchdog timeout in sub-seconds? Alexander Stein
2015-04-13 13:53 ` Guenter Roeck
2015-04-14 8:15 ` Alexander Stein [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=4398543.5EAQg64u7T@ws-stein \
--to=alexander.stein@systec-electronic.com \
--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