From: Andi Kleen <andi@firstfloor.org>
To: "Woodruff, Richard" <r-woodruff2@ti.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
linux-pm@lists.linux-foundation.org, lenb@kernel.org
Subject: Re: Higer latency with dynamic tick (need for an io-ondemand govenor?)
Date: Sun, 20 Apr 2008 16:26:33 +0200 [thread overview]
Message-ID: <480B5299.9090904@firstfloor.org> (raw)
In-Reply-To: <3B6D69C3A9EBCA4BA5DA60D9130274290413207D@dlee13.ent.ti.com>
Woodruff, Richard wrote:
> "Andi Kleen" <andi@firstfloor.org> writes:
>> Are you talking about x86?
>
> ARM (TI-OMAP)
Sorry I was confused because you used the term "C-state" which is normally ACPI (x86/ia64)
specific. If someone says C states I assume ACPI and usually x86 by default
due to lack of deeper sleep states on most ia64s.
> Not sure about the underlying X86 hardware implementation.
On x86 the trend is for the hardware/firmware/SMM doing more and more of this on its own,
as in deciding by itself how deep it wants to sleep.
-Andi
prev parent reply other threads:[~2008-04-20 14:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 23:20 bug seen with dynticks from CONFIG_HARDIRQS_SW_RESEND Woodruff, Richard
2007-05-17 10:10 ` Thomas Gleixner
2007-05-17 20:14 ` Woodruff, Richard
2007-05-17 20:38 ` Thomas Gleixner
2007-05-17 22:24 ` Woodruff, Richard
2007-05-18 7:49 ` Thomas Gleixner
2008-04-18 15:43 ` Higer latency with dynamic tick (need for an io-ondemand govenor?) Woodruff, Richard
2008-04-19 3:45 ` [linux-pm] " David Brownell
2008-04-19 7:13 ` Thomas Gleixner
2008-04-19 22:49 ` david
2008-04-20 3:51 ` David Brownell
2008-04-20 6:19 ` Arjan van de Ven
2008-04-20 14:09 ` Woodruff, Richard
2008-04-20 12:41 ` Andi Kleen
2008-04-20 14:21 ` Woodruff, Richard
2008-04-20 14:26 ` Andi Kleen [this message]
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=480B5299.9090904@firstfloor.org \
--to=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=mingo@elte.hu \
--cc=r-woodruff2@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox