From: Eric Dumazet <eric.dumazet@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Colin Ian King <colin.king@canonical.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] softlockup: stop spurious softlockup messages due to overflow
Date: Thu, 18 Mar 2010 21:45:10 +0100 [thread overview]
Message-ID: <1268945110.2894.162.camel@edumazet-laptop> (raw)
In-Reply-To: <20100318152535.GB12564@elte.hu>
Le jeudi 18 mars 2010 à 16:25 +0100, Ingo Molnar a écrit :
> * Colin Ian King <colin.king@canonical.com> wrote:
>
> >
> > Using time_after/before:
> >
> > diff --git a/kernel/softlockup.c b/kernel/softlockup.c
> > index 0d4c789..4b493f6 100644
> > --- a/kernel/softlockup.c
> > +++ b/kernel/softlockup.c
> > @@ -155,11 +155,11 @@ void softlockup_tick(void)
> > * Wake up the high-prio watchdog task twice per
> > * threshold timespan.
> > */
> > - if (now > touch_ts + softlockup_thresh/2)
> > + if (time_after(now - softlockup_thresh/2, touch_ts))
> > wake_up_process(per_cpu(softlockup_watchdog, this_cpu));
> >
> > /* Warn about unreasonable delays: */
> > - if (now <= (touch_ts + softlockup_thresh))
> > + if (time_before_eq(now - softlockup_thresh, touch_ts))
> > return;
>
> Ok, that looks like the most readable variant, agreed?
>
Sure ! Colin please submit formally your patch :)
Thanks
next prev parent reply other threads:[~2010-03-18 20:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 14:01 Colin Ian King
2010-03-15 14:29 ` Eric Dumazet
2010-03-16 10:12 ` Ingo Molnar
2010-03-18 13:22 ` Colin Ian King
2010-03-18 15:25 ` Ingo Molnar
2010-03-18 20:45 ` Eric Dumazet [this message]
2010-03-19 10:28 ` Colin Ian King
2010-03-22 7:45 ` [tip:core/urgent] softlockup: Stop " tip-bot for Colin Ian King
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=1268945110.2894.162.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=colin.king@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®