From: Jens Axboe <axboe@suse.de>
To: Jon Escombe <lists@dresco.co.uk>
Cc: Pavel Machek <pavel@suse.cz>, Adam Goode <adam@evdebs.org>,
Alejandro Bonilla Beeche <abonilla@linuxwireless.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
hdaps devel <hdaps-devel@lists.sourceforge.net>
Subject: Re: [Hdaps-devel] Re: HDAPS, Need to park the head for real
Date: Fri, 19 Aug 2005 12:23:15 +0200 [thread overview]
Message-ID: <20050819102314.GN6273@suse.de> (raw)
In-Reply-To: <4305AECE.3020508@dresco.co.uk>
On Fri, Aug 19 2005, Jon Escombe wrote:
>
> >>>>Please make it "echo 1 > frozen", then userspace can do "echo 0 >
> >>>>frozen"
> >>>>after five seconds.
> >>>>
> >>>>
> >>>What if the code to do "echo 0 > frozen" is swapped out to disk? ;)
> >>>
> >>>
> >>Emergency head parker needs to be pagelocked for other reasons. You do
> >>not want to page it from disk while your notebook is in free fall.
> >>
> >>
> >
> >It's still a very bad idea imho, what if the head parker daemon is
> >killed for other reasons? The automatic timeout thawing the drive is
> >much saner.
> >
> >
> For hard disk protection, I prefer the idea of the userspace code
> thawing the drive based on current accelerometer data, rather than
> simply waking up after x seconds (maybe you're running for a bus rather
> than falling off a table)...
>
> To get the best of both worlds, could we maybe take a watchdog timer
> approach, and have the timeout reset by the userspace component
> periodically re-requesting freeze?
That would work, you can just define the semantics to be that echo
foo > frozen would add foo seconds to the timeout (or thaw it, if foo is
0).
--
Jens Axboe
next prev parent reply other threads:[~2005-08-19 10:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 15:25 HDAPS, Need to park the head for real Alejandro Bonilla Beeche
2005-08-16 15:34 ` Lee Revell
2005-08-16 15:41 ` Alejandro Bonilla Beeche
2005-08-16 20:07 ` Jens Axboe
2005-08-16 23:15 ` Alejandro Bonilla Beeche
2005-08-16 23:29 ` [Hdaps-devel] " Yani Ioannou
2005-08-17 5:53 ` Jens Axboe
2005-08-17 6:23 ` [Hdaps-devel] " Jon Escombe
2005-08-17 7:47 ` Avi Kivity
2005-08-17 7:56 ` Jens Axboe
2005-08-18 20:49 ` Pavel Machek
2005-08-18 21:15 ` Adam Goode
2005-08-18 21:30 ` [Hdaps-devel] " Dave Hansen
2005-08-18 21:38 ` Pavel Machek
2005-08-19 6:36 ` Jens Axboe
2005-08-19 10:05 ` [Hdaps-devel] " Jon Escombe
2005-08-19 10:23 ` Jens Axboe [this message]
2005-08-19 12:41 ` Alejandro Bonilla
2005-08-24 21:44 ` Jon Escombe
2005-08-25 10:57 ` Alan Cox
2005-08-25 18:14 ` Jon Escombe
2005-08-26 6:49 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2005-08-19 11:36 Stefan Rompf
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=20050819102314.GN6273@suse.de \
--to=axboe@suse.de \
--cc=abonilla@linuxwireless.org \
--cc=adam@evdebs.org \
--cc=hdaps-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@dresco.co.uk \
--cc=pavel@suse.cz \
/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