From: Zwane Mwaikambo <zwane@linuxpower.ca>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Intel thermal monitor for x86_64 (updated)
Date: Thu, 18 Nov 2004 14:57:53 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.4.61.0411181457260.7988@musoma.fsmlabs.com> (raw)
In-Reply-To: <20041118200143.GP17532@wotan.suse.de>
On Thu, 18 Nov 2004, Andi Kleen wrote:
> Flooding the kmsg is as bad.
>
> I think a better strategy is to just increase the minimum check interval
> to avoid this. And then treat printk and mce_log the same.
>
> >
> > > Also the next_check logic should already handle this I guess,
> > > becaumse I assume the temperature dropping won't take
> > > that long. So I guess it would be best to drop that
> > > and if it's still a problem use a longer next_check timeout
> > > of several seconds.
> >
> > The temperature drop can take a while, i've observed 2-3 minutes if the
> > processor is also loaded and the ambient temperature is low (20C). So you
> > could lose 12 or so slots in the mce log due to the temperature ping
> > ponging.
>
> Ok then perhaps a extremly long check timeout of 5 minutes?
Agreed, i'll have something tommorrow.
Thanks for the input,
Zwane
next prev parent reply other threads:[~2004-11-18 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-18 15:49 [PATCH] Intel thermal monitor for x86_64 (updated) Zwane Mwaikambo
2004-11-18 16:33 ` Andi Kleen
2004-11-18 17:58 ` Zwane Mwaikambo
2004-11-18 20:01 ` Andi Kleen
2004-11-18 21:57 ` Zwane Mwaikambo [this message]
2004-11-19 15:51 ` Zwane Mwaikambo
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=Pine.LNX.4.61.0411181457260.7988@musoma.fsmlabs.com \
--to=zwane@linuxpower.ca \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).