From: Johannes Weiner <hannes@saeurebad.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 3/3] softlockup: fix watchdog task wakeup frequency
Date: Fri, 27 Jun 2008 14:33:40 +0200 [thread overview]
Message-ID: <87prq3xdjv.fsf@skyscraper.fehenstaub.lan> (raw)
In-Reply-To: <20080627120350.GB30872@elte.hu> (Ingo Molnar's message of "Fri, 27 Jun 2008 14:03:50 +0200")
Ingo Molnar <mingo@elte.hu> writes:
> * Johannes Weiner <hannes@saeurebad.de> wrote:
>
>> Wake up the watchdog every second instead of every second. [...]
>
> now _that_ is a real improvement ;-)
>
>> /* Wake up the high-prio watchdog task every second: */
>> - if (now > (touch_timestamp + 1))
>> + if (now > touch_timestamp)
>> wake_up_process(per_cpu(watchdog_task, this_cpu));
>
> you mean wake up every second instead of every two seconds?
Every second second :D The second `second' [adjective] refers to the
first `second' [noun].
> i think the best sleep period for the watchdog is half of the threshold.
> It makes no point to check sooner than that. I.e. softlockup_thresh/2
> would be better?
Hm, it updates the timestamp, so it makes only sense if it runs at a
maximum every second (timestamp granularity) or even less. The check
for hung tasks uses the cpu timestamp as well for comparison, so that
would be okay too.
Like this?
diff --git a/kernel/softlockup.c b/kernel/softlockup.c
index c828c23..b884546 100644
--- a/kernel/softlockup.c
+++ b/kernel/softlockup.c
@@ -106,8 +106,9 @@ void softlockup_tick(void)
now = get_timestamp(this_cpu);
- /* Wake up the high-prio watchdog task every second: */
- if (now > (touch_timestamp + 1))
+ /* Wake up the high-prio watchdog task twice per
+ * threshold timespan. */
+ if (now > (touch_timestamp + softlockup_thresh / 2))
wake_up_process(per_cpu(watchdog_task, this_cpu));
/* Warn about unreasonable delays: */
next prev parent reply other threads:[~2008-06-27 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 0:04 [PATCH 0/3] softlockup fixlets Johannes Weiner
2008-06-27 0:04 ` [PATCH 1/3] softlockup: only reset timestamp from NMI code Johannes Weiner
2008-06-27 0:04 ` [PATCH 2/3] softlockup: sanitize print-out limit checks Johannes Weiner
2008-06-27 0:04 ` [PATCH 3/3] softlockup: fix watchdog task wakeup frequency Johannes Weiner
2008-06-27 12:03 ` Ingo Molnar
2008-06-27 12:33 ` Johannes Weiner [this message]
2008-06-27 12:43 ` Ingo Molnar
2008-06-27 13:07 ` Johannes Weiner
2008-06-28 0:45 ` Johannes Weiner
2008-06-30 13:08 ` Ingo Molnar
2008-07-01 5:40 ` Johannes Weiner
2008-07-01 6:11 ` Ingo Molnar
2008-07-01 7:12 ` Johannes Weiner
2008-07-01 7:22 ` Ingo Molnar
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=87prq3xdjv.fsf@skyscraper.fehenstaub.lan \
--to=hannes@saeurebad.de \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome