From: Pascal Vandeputte <pascal@asmodeus.be>
To: Tejun Heo <tj@kernel.org>
Cc: "Ivan N. Zlatev" <contact@i-nz.net>,
Robert Krawitz <rlk@alum.mit.edu>, Omar A <aliencoder@gmail.com>,
Carlos Bessa <carlos.bessa@gmail.com>,
Andy Vaselaar <andrew.vaselaar@trinity.edu>,
webmaster@dragontower.de, Christian Wolf <wolfchri@gmail.com>,
"A. Klitzing" <aklitzing@online.de>,
Stefan Henriet <aladin7501-01@yahoo.de>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: regarding frequent head unload problem
Date: Mon, 29 Sep 2008 23:12:17 +0200 [thread overview]
Message-ID: <48E144B1.1070508@asmodeus.be> (raw)
In-Reply-To: <48E08B99.1070508@kernel.org>
Tejun Heo wrote:
> Hello,
>
> I'm writing to everyone who reported to me or linux-ide about frequent
> head unload problem and the report is not yet committed to
> storage-fixup.conf.
>
> I'm a bit worried about the explosion of reports because I really
> wanna avoid creating false entries as they will increase power
> consumption on Linux unnecessarily. [...]
Hi,
I understand your concern. It mainly comes down to how much earlier your
battery is drained I guess (without taking the "green" aspect into
account). Would anyone have any numbers on that? If not, we could do a
test ourselves (torturing our drives for a few hours extra,
percentage-wise the extra wear and tear is limited).
The amount of power saved will probably differ between drive
manufacturers & models as well. My gut feeling is that it won't make
that much of a difference, but it's indeed something to think about.
Greetings,
Pascal
prev parent reply other threads:[~2008-09-29 21:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48E08B99.1070508@kernel.org>
2008-09-29 9:00 ` regarding frequent head unload problem Paul Rolland
2008-09-29 18:41 ` Paul Rolland
2008-09-29 11:44 ` Robert Krawitz
2008-09-29 16:34 ` Omar A
2008-09-29 21:12 ` Pascal Vandeputte [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=48E144B1.1070508@asmodeus.be \
--to=pascal@asmodeus.be \
--cc=aklitzing@online.de \
--cc=aladin7501-01@yahoo.de \
--cc=aliencoder@gmail.com \
--cc=andrew.vaselaar@trinity.edu \
--cc=carlos.bessa@gmail.com \
--cc=contact@i-nz.net \
--cc=linux-ide@vger.kernel.org \
--cc=rlk@alum.mit.edu \
--cc=tj@kernel.org \
--cc=webmaster@dragontower.de \
--cc=wolfchri@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).