From: Pavel Machek <pavel@suse.cz>
To: Eric Piel <eric.piel@tremplin-utc.net>
Cc: Theodore Tso <tytso@mit.edu>, Robert Hancock <hancockr@shaw.ca>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Gabor Gombas <gombasg@sztaki.hu>, Tejun Heo <htejun@gmail.com>,
Elias Oltmanns <eo@nebensachen.de>, Jeff Garzik <jeff@garzik.org>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/5] libata: Implement disk shock protection support
Date: Tue, 5 Aug 2008 22:00:21 +0200 [thread overview]
Message-ID: <20080805200021.GF7939@elf.ucw.cz> (raw)
In-Reply-To: <48986E3A.5020707@tremplin-utc.net>
On Tue 2008-08-05 17:14:02, Eric Piel wrote:
> Theodore Tso schreef:
>> The real right answer though is to buy one of the laptop drives (such
>> as the Seagate Momentus 7200.2 or 7200.3) which has the anti-shock
>> detection built directly into the hard drive. That way you don't have
>> to have a daemon that sits in the OS waking up the CPU some 20 to 30
>> times a second and burning up your battery even when the laptop is
>> idle.
> Well, it's not always _that_ bad. For instance, the accelerometer in the HP
> laptops (lis3lv02dl) can monitor free-falls by itself. When the laptop
> starts falling, it generates one interrupt.
I was told that "when it starts falling" is too late.
Thinkpads at least tried to detect the movement before fall: before
notebook falls off table, it is very likely to tilt a lot.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-08-05 19:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.nx0yFPJm+aNXPHgykUrOzZXvvIs@ifi.uio.no>
[not found] ` <fa.NfEr7Ik6e8oextyWICW/jR5emeE@ifi.uio.no>
[not found] ` <fa.zGvATZImeUo0tHJe4hzlk5+mTiM@ifi.uio.no>
[not found] ` <fa.SRVleMItV5QEF7/tgCjSHz0ScJA@ifi.uio.no>
[not found] ` <fa.YKbhgq8XUxH/Qg1ArE+73YsDlpE@ifi.uio.no>
2008-08-05 4:05 ` [PATCH 3/5] libata: Implement disk shock protection support Robert Hancock
2008-08-05 13:14 ` Theodore Tso
2008-08-05 14:29 ` Henrique de Moraes Holschuh
2008-08-05 15:14 ` Eric Piel
2008-08-05 19:59 ` Pavel Machek
2008-08-05 22:57 ` Elias Oltmanns
[not found] ` <48986E3A.5020707@tremplin-utc.net>
2008-08-05 20:00 ` Pavel Machek [this message]
2008-08-05 4:16 ` Robert Hancock
2008-08-05 7:49 ` Tejun Heo
2008-07-26 6:20 [RFC] Disk shock protection in GNU/Linux Elias Oltmanns
2008-07-26 6:25 ` [PATCH 3/5] libata: Implement disk shock protection support Elias Oltmanns
2008-08-01 7:19 ` Tejun Heo
2008-08-01 22:34 ` Alan Cox
2008-08-03 3:19 ` Tejun Heo
2008-08-03 13:05 ` Alan Cox
2008-08-03 13:58 ` Tejun Heo
2008-08-04 13:43 ` Elias Oltmanns
2008-08-04 13:26 ` Elias Oltmanns
2008-08-04 14:12 ` Tejun Heo
2008-08-04 16:54 ` Elias Oltmanns
2008-08-04 23:26 ` Tejun Heo
2008-08-04 14:28 ` Gabor Gombas
2008-08-04 14:13 ` Alan Cox
2008-08-04 14:35 ` Tejun Heo
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=20080805200021.GF7939@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=James.Bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bzolnier@gmail.com \
--cc=eo@nebensachen.de \
--cc=eric.piel@tremplin-utc.net \
--cc=gombasg@sztaki.hu \
--cc=hancockr@shaw.ca \
--cc=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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).