From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Stéphane ANCELOT" <sancelot@free.fr>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] intel turbo boost
Date: Sun, 8 Nov 2015 12:26:27 +0100 [thread overview]
Message-ID: <20151108112627.GL1798@hermes.click-hack.org> (raw)
In-Reply-To: <20151104003032.GB24848@hermes.click-hack.org>
On Wed, Nov 04, 2015 at 01:30:32AM +0100, Gilles Chanteperdrix wrote:
> On Thu, Sep 03, 2015 at 09:00:36AM +0200, Stéphane ANCELOT wrote:
> > Hi,
> >
> > Do you think I can use the Intel integrated turbo boost mode, without
> > problems.
> >
> > I have this nice processor :
> > http://ark.intel.com/fr/products/76308/Intel-Core-i5-4300U-Processor-3M-Cache-up-to-2_90-GHz
>
> Just experimented this, the turbo mode is a problem for applications
> which rely on a precise relation between the actual count of cpu
> cycles of a busy loop and the time. The sched_quota falls under that
> category and simply does not work reliably when turbo mode is
> enabled. Fortunately, it is possible to turn off turbo mode. For
> that, in the kernel configuration
> - enable CPU_FREQ
> - choose performance mode by default
> - enable intel pstate driver
> - echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo
>
> Other than that, turbo mode does not seem to break the latency,
> which would mean that the tsc frequency does not change with turbo
> mode.
Turbo mode also breaks the autotune feature. So, on a machine with
turbo mode, autotune should be triggered after writing to the /proc
file.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2015-11-08 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 7:00 [Xenomai] intel turbo boost Stéphane ANCELOT
2015-11-04 0:30 ` Gilles Chanteperdrix
2015-11-08 11:26 ` Gilles Chanteperdrix [this message]
2015-11-12 8:20 ` Stéphane ANCELOT
2015-11-12 9:54 ` Philippe Gerum
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=20151108112627.GL1798@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=sancelot@free.fr \
--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.