From: Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: does cpu_idle() halt CPU?
Date: Wed, 02 Apr 2003 09:05:06 +0200 [thread overview]
Message-ID: <m24r5hwfa5.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: <20030329134742.GD10287-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org> (Ducrot Bruno's message of "Sat, 29 Mar 2003 14:47:42 +0100")
>>>>> "DB" == Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>:
[...]
DB> You forgot at least disk activities especially if ext3, which
DB> prevent almost all IDE drivers to go to idle state. But that will
DB> not explain why you can not go to C3 though.
By the way, let me ask here: does anybody know what would be the best
filesystem to use on a laptop, power saving being the #1 priority? Are
all journaling filesystems this bad?
There was a project to teach the Linux kernel about drive spindown and
manage drive accesses accordingly -- but last time I saw their docs they
said that all journaling filesystems pose serious problems...
USB preventing the machine from going into C3 is a serious problem. I
still don't understand if that's a hardware thing or can we have a more
reasonable HCI implementation that doesn't use DMA that much. How does
Windows deal with it?
--J.
-------------------------------------------------------
This SF.net email is sponsored by: ValueWeb:
Dedicated Hosting for just $79/mo with 500 GB of bandwidth!
No other company gives more support or power for your dedicated server
http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/
next prev parent reply other threads:[~2003-04-02 7:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 22:43 does cpu_idle() halt CPU? Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847E96D88-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-28 23:02 ` Jun Sun
[not found] ` <20030328150218.D10287-Ht5ggzGNZTC9Yl/XQThFG6xOck334EZe@public.gmane.org>
2003-03-29 13:47 ` Ducrot Bruno
[not found] ` <20030329134742.GD10287-j6u/t2rXLliUoIHC/UFpr9i2O/JbrIOy@public.gmane.org>
2003-04-02 7:05 ` Jan Rychter [this message]
[not found] ` <m24r5hwfa5.fsf-dTJq59+VGzkkCw8IV3R6h0EOCMrvLtNR@public.gmane.org>
2003-04-02 21:42 ` Matthew Keller
[not found] ` <1049319771.19172.27.camel-a2ysWtvtB4BRjtM+DFHcO/Z8FUJU4vz8@public.gmane.org>
2003-04-03 6:47 ` Karol Kozimor
[not found] ` <20030403064726.GA27821-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
2003-04-03 18:22 ` Matthew Keller
[not found] ` <1049394142.5251.7.camel-a2ysWtvtB4BRjtM+DFHcO/Z8FUJU4vz8@public.gmane.org>
2003-04-03 22:45 ` Jan Rychter
2003-04-02 21:44 ` Charl P. Botha
-- strict thread matches above, loose matches on Subject: below --
2003-03-31 18:15 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A847E96D94-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-04-11 19:45 ` Ben Slusky
2003-03-28 22:28 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A23A-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-03-28 22:37 ` Jun Sun
2003-03-29 10:10 ` Stephan Krings
[not found] ` <16005.28938.409919.994510-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-03-29 15:20 ` Jun Sun
2003-03-28 22:19 Jun Sun
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=m24r5hwfa5.fsf@tnuctip.rychter.com \
--to=jan-jaspcfd0eodbdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox