From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Tobias Luksch <Tobias.Luksch@itk-engineering.de>
Cc: "Xenomai@xenomai.org" <Xenomai@xenomai.org>,
Kurijn Buys <Kurijn.Buys@open.ac.uk>
Subject: Re: [Xenomai] latency spikes under load
Date: Wed, 11 Dec 2013 18:21:24 +0100 [thread overview]
Message-ID: <52A89F14.8020104@xenomai.org> (raw)
In-Reply-To: <1124806E0C09F04A992E69AE2EC7FA3CB1B138@swexchange01.itk.local>
On 12/11/2013 05:04 PM, Tobias Luksch wrote:
>>> On Wed, Dec 11, 2013 at 02:23:38PM +0000, Kurijn Buys wrote: I
>>> enabled APIC, and the latency peaks at 16us only now, and even
>>> less with
>> load.
>>> This also had an effect on my analogy problem, but not
>>> completely... I will
>> start a new thread for that...
>>
>> If your latency drops under loads, it sounds as if your CPU is
>> slowing down when idle and taking a while to speed back up.
>> Perhaps changing the CPU governer to performance or user controlled
>> and setting a fixed CPU speed would keep the latency low all the
>> time (although at the cost of more power consumption).
>
> I had a similar problem where the latency behavior changed depending
> on the CPU load on an Intel CPU (see " Problems with running Xenomai
> on Core i5" thread of this list). It turned out to be a C1E "feature"
> that I could not influence in the BIOS. But clearing the second bit
> of the MSR_IA32_POWER_CTL register did help. I used the wrmsr command
> of the msr-tools package.
Ok, we could integrate this C1E workaround as the SMI workaround or AMD
C1E workaround. Do you have any pointer, which would explain me a way to
detect that this MSR is available (and C1E is enabled, but I guess it is
just a matter of reading the MSR). Second question is: has not this
change any repercussion on processor temperature.
--
Gilles.
next prev parent reply other threads:[~2013-12-11 17:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 11:38 [Xenomai] latency spikes under load Kurijn Buys
2013-12-03 11:54 ` Gilles Chanteperdrix
2013-12-03 12:31 ` Gilles Chanteperdrix
2013-12-03 13:07 ` Kurijn Buys
2013-12-03 13:23 ` Gilles Chanteperdrix
2013-12-03 15:31 ` Kurijn Buys
2013-12-03 15:54 ` Gilles Chanteperdrix
2013-12-03 16:49 ` Kurijn Buys
2013-12-03 18:50 ` Gilles Chanteperdrix
2013-12-04 8:44 ` Philippe Gerum
2013-12-04 8:51 ` Gilles Chanteperdrix
2013-12-04 9:27 ` Philippe Gerum
2013-12-04 9:31 ` Gilles Chanteperdrix
2013-12-04 9:40 ` Philippe Gerum
2013-12-04 9:51 ` Gilles Chanteperdrix
2013-12-04 10:29 ` Philippe Gerum
2013-12-04 10:33 ` Philippe Gerum
2013-12-04 11:04 ` Philippe Gerum
2013-12-04 11:10 ` Gilles Chanteperdrix
2013-12-04 11:36 ` Philippe Gerum
2013-12-04 11:59 ` Philippe Gerum
2013-12-04 12:00 ` Gilles Chanteperdrix
2013-12-04 13:19 ` Philippe Gerum
2013-12-04 16:03 ` Gilles Chanteperdrix
2013-12-04 17:43 ` Philippe Gerum
2013-12-05 0:44 ` Kurijn Buys
2013-12-05 10:28 ` Kurijn Buys
2013-12-05 11:05 ` Philippe Gerum
2013-12-05 11:09 ` Gilles Chanteperdrix
2013-12-09 15:19 ` Kurijn Buys
2013-12-09 15:27 ` Gilles Chanteperdrix
2013-12-11 14:23 ` Kurijn Buys
2013-12-11 14:51 ` Lennart Sorensen
2013-12-11 16:04 ` Tobias Luksch
2013-12-11 17:21 ` Gilles Chanteperdrix [this message]
2013-12-11 16:44 ` [Xenomai] Analogy NI 6052E Kurijn Buys
2014-03-21 14:33 ` Erhart Robert (CC-DA/ESR3)
2014-03-22 16:58 ` Gilles Chanteperdrix
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=52A89F14.8020104@xenomai.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=Kurijn.Buys@open.ac.uk \
--cc=Tobias.Luksch@itk-engineering.de \
--cc=Xenomai@xenomai.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 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.