* Watchdog thread activity
@ 2017-11-14 15:04 Sriram V
2017-11-14 16:14 ` Guenter Roeck
0 siblings, 1 reply; 2+ messages in thread
From: Sriram V @ 2017-11-14 15:04 UTC (permalink / raw)
To: linux-watchdog
Hi,
I am running Linux along with image processing on my system.
Most watchdogs i have seen previously, has a 30 second/60 second
timer. The watchdog we have used currently has a fixed timeout value
of 1.6 seconds.
I wanted to check if Linux can pet the watchdog say every 1 second.
Won't it over-load the system if i used mod_timer/workqueue?
However, I think, Some activity in the system might cause false-resets
due to the cpu being busy in other tasks.
Therefore, i wanted to check what is the safe minimum duration which
will avoid false-resets.
Thanks,
sriram
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Watchdog thread activity
2017-11-14 15:04 Watchdog thread activity Sriram V
@ 2017-11-14 16:14 ` Guenter Roeck
0 siblings, 0 replies; 2+ messages in thread
From: Guenter Roeck @ 2017-11-14 16:14 UTC (permalink / raw)
To: Sriram V; +Cc: linux-watchdog
On Tue, Nov 14, 2017 at 08:34:03PM +0530, Sriram V wrote:
> Hi,
>
> I am running Linux along with image processing on my system.
> Most watchdogs i have seen previously, has a 30 second/60 second
> timer. The watchdog we have used currently has a fixed timeout value
> of 1.6 seconds.
>
> I wanted to check if Linux can pet the watchdog say every 1 second.
> Won't it over-load the system if i used mod_timer/workqueue?
>
> However, I think, Some activity in the system might cause false-resets
> due to the cpu being busy in other tasks.
>
> Therefore, i wanted to check what is the safe minimum duration which
> will avoid false-resets.
>
Why don't you just use the existing watchdog subsystem infrastructure,
which does support that use case ? Do you have any evidence that it fails
under some circumstances ? If so, can you let us know how to trigger that
failure so we can understand it and find a possible fix ?
Thanks,
Guenter
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-11-14 16:14 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-11-14 15:04 Watchdog thread activity Sriram V
2017-11-14 16:14 ` Guenter Roeck
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.