From: Tony Lindgren <tony@atomide.com>
To: Andi Kleen <ak@suse.de>
Cc: Len Brown <len.brown@intel.com>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>,
Rajesh Shah <rajesh.shah@intel.com>,
John Stultz <johnstul@us.ibm.com>,
Asit K Mallick <asit.k.mallick@intel.com>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
trenn@suse.de
Subject: Re: [RFC][PATCH] i386 x86-64 Eliminate Local APIC timer interrupt
Date: Wed, 11 May 2005 11:12:15 -0700 [thread overview]
Message-ID: <20050511181214.GH15479@atomide.com> (raw)
In-Reply-To: <20050505121924.GN28441@wotan.suse.de>
* Andi Kleen <ak@suse.de> [050505 05:21]:
> On Thu, May 05, 2005 at 01:33:33AM -0400, Brown, Len wrote:
> > Re: no idle tick
> >
> > Idle power savings does not by itself justify HZ=0.
> > We'll get the same idle power consumption with HZ=1.
>
>
> Power consumption is not the only reason for no tick in idle.
> The other big one is virtualization. If you have lots
> of virtual machines running on a hypervisor you really
> dont want them to wake up regularly even when idle.
Yes, and although this is x86/x86_64 thread, I'd like to point out
that embedded systems can benefit from skipping ticks for several
seconds at a time.
There's no need for ticks on embedded systems until some event,
such as an interrupt happens.
Cheers,
Tony
next prev parent reply other threads:[~2005-05-11 18:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 0:26 [RFC][PATCH] i386 x86-64 Eliminate Local APIC timer interrupt Venkatesh Pallipadi
2005-04-30 0:46 ` Zwane Mwaikambo
2005-04-30 0:58 ` Zwane Mwaikambo
2005-04-30 1:13 ` Zwane Mwaikambo
2005-04-30 2:32 ` Andrew Morton
2005-05-02 16:38 ` Andi Kleen
2005-05-02 17:16 ` Venkatesh Pallipadi
2005-05-02 19:08 ` Andi Kleen
2005-05-02 20:27 ` Venkatesh Pallipadi
2005-05-03 14:17 ` Andi Kleen
2005-05-05 5:33 ` Len Brown
2005-05-05 12:19 ` Andi Kleen
2005-05-11 18:12 ` Tony Lindgren [this message]
2005-05-05 20:45 ` George Anzinger
-- strict thread matches above, loose matches on Subject: below --
2005-04-30 2:43 Pallipadi, Venkatesh
2005-05-05 4:16 ` Len Brown
2005-05-05 12:03 ` Andi Kleen
2005-05-05 12:32 ` Maciej W. Rozycki
2005-04-30 2:55 Pallipadi, Venkatesh
2005-04-30 3:06 ` Andrew Morton
2005-05-02 21:19 ` Pavel Machek
2005-04-30 19:40 Protasevich, Natalie
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=20050511181214.GH15479@atomide.com \
--to=tony@atomide.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=asit.k.mallick@intel.com \
--cc=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rajesh.shah@intel.com \
--cc=torvalds@osdl.org \
--cc=trenn@suse.de \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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