From: Tim Blechmann <tim@klingt.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: scheduling latency & CONFIG_HZ
Date: Sat, 14 Nov 2009 11:48:09 +0100 [thread overview]
Message-ID: <4AFE8AE9.3050804@klingt.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0911132133250.24119@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]
>> i am curious, do the values of CONFIG_HZ and CONFIG_NO_HZ somehow affect the
>> scheduling latency (as reported by cyclictest) of a real-time/vanilla kernel,
>> especially when CONFIG_HIGH_RES_TIMERS is enabled?
>
> CONFIG_HZ should be pretty irrelevant, but CONFIG_NO_HZ=y especially
> when the CPU does support deeper C-States and the ACPI cpuidle support
> is active may influence it simply because the wake up from deeper
> c-states can take significantly longer than waking up from C1 (the
> default halt state). Note that the wakeup latency from C-States
> depends on the CPU model, chipset, available timer hardware ...
interesting ... from my understanding, the wakeup latency is known to
the kernel (/sys/devices/system/cpu/cpuX/cpuidle/stateY/latency) and is
taken into account when governor selects the next state ... is it
possible to tweak the governor by setting the latency requirement
(pm_qos_requirement(PM_QOS_CPU_DMA_LATENCY)) from userspace?
thanks, tim
--
tim@klingt.org
http://tim.klingt.org
Lesser artists borrow, great artists steal.
Igor Stravinsky
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-14 10:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 18:44 scheduling latency & CONFIG_HZ Tim Blechmann
2009-11-13 20:37 ` Thomas Gleixner
2009-11-14 10:48 ` Tim Blechmann [this message]
2009-11-21 2:32 ` Frank Rowand
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=4AFE8AE9.3050804@klingt.org \
--to=tim@klingt.org \
--cc=linux-rt-users@vger.kernel.org \
--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 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.