All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Carsten Emde <C.Emde@osadl.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <williams@redhat.com>,
	Stefan Roese <stefan.roese@gmail.com>,
	linux-rt-users@vger.kernel.org
Subject: Re: cyclictest better values with system load than without (OMAP3530 target)
Date: Fri, 29 Nov 2013 17:36:34 +0100	[thread overview]
Message-ID: <5298C292.2030502@xenomai.org> (raw)
In-Reply-To: <5298AE4B.7070806@osadl.org>

On 11/29/2013 04:10 PM, Carsten Emde wrote:
> BTW: Power saving and real-time do not necessarily exclude each other.
> If a - still deterministic - but a little longer latency is acceptable,
> some light sleep states and a somewhat lower clock frequency may be
> allowed which still may result in considerable energy saving. If,
> however, the fastest possible real-time response is required, C states
> and P states must be disabled (or set to polling and maximum speed,
> repsectively) and the power bill must be payed.

Well, I do not fully agree. To be sure that you can clock down the 
processor for executing a task which has sufficient time to meet its 
deadline, your system must be "time triggered", all the timer events 
must be known in advance. Because on a fully dynamic system, you may 
make that decision, but a new timer may be scheduled which causes the 
system to miss its deadline whereas it would not have missed it if it 
had run at full speed.

-- 
					    Gilles.

  reply	other threads:[~2013-11-29 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26  9:21 cyclictest better values with system load than without (OMAP3530 target) Stefan Roese
2013-11-26 14:21 ` Dmitry Lysenko
2013-11-26 19:14   ` Stefan Roese
2013-11-26 20:14     ` Tim Sander
2013-11-26 16:12 ` Clark Williams
2013-11-29 12:56   ` Sebastian Andrzej Siewior
2013-11-29 15:10     ` Carsten Emde
2013-11-29 16:36       ` Gilles Chanteperdrix [this message]
2013-11-29 16:58         ` Gilles Chanteperdrix
2013-11-29 17:36           ` Carsten Emde
2013-11-29 19:34             ` Gilles Chanteperdrix
2013-11-29 21:10               ` Carsten Emde

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=5298C292.2030502@xenomai.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=stefan.roese@gmail.com \
    --cc=williams@redhat.com \
    /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.