summaryrefslogtreecommitdiffstats
path: root/tools/regression/lib/libc/stdlib
diff options
context:
space:
mode:
authordelphij <delphij@FreeBSD.org>2014-11-16 09:44:30 +0000
committerdelphij <delphij@FreeBSD.org>2014-11-16 09:44:30 +0000
commitfd6ff343405de58a34f9a74df470ad546bab6244 (patch)
treef60239e7d4bbd25ad2cac0ea260d966f7d2b03b4 /tools/regression/lib/libc/stdlib
parentac2aadeb0398c610421d53451615e9f5364858ba (diff)
downloadFreeBSD-src-fd6ff343405de58a34f9a74df470ad546bab6244.zip
FreeBSD-src-fd6ff343405de58a34f9a74df470ad546bab6244.tar.gz
Default to use 10 seconds as nap interval instead of 1.
Previously, we have a nap interval of 1 second while we have a timeout of 128 seconds by default, which could be an overkill, and for some hardware the patting action may be expensive. Note that the choice of nap interval is still arbitrary. We preferred a safe value where even when the system is very heavily loaded, the watchdog should not shoot the system down if it's not really hung. According to the manual page of Linux's watchdog daemon, the nap interval time of theirs is 10 seconds, which seems to be a reasonable value -- according to Intel documentation AP-725 (Document Number: 292273-001), ICH5's maximum timeout is about 37.5 seconds, which the ichwd(4) driver would set when we requested 128 seconds (although it should probably feed back this as an error and do not set the timeout). Since that's the shortest maximum value, 10 seconds seems to be a right choice for us too. Discussed with: alfred MFC after: 1 month
Diffstat (limited to 'tools/regression/lib/libc/stdlib')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud