public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lenz Grimmer <lenz@grimmer.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Gijs Hillenius <gijs@hillenius.net>,
	Frank Sorenson <frank@tuxrocks.com>,
	hdaps-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [Hdaps-devel] Re: Updating hard disk firmware & parking hard disk
Date: Wed, 13 Jul 2005 12:21:21 +0200	[thread overview]
Message-ID: <42D4EB21.1060305@grimmer.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0507131208540.14635@yvahk01.tjqt.qr>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jan Engelhardt wrote:

> Head parking while the system running is almost useless, since sooner or 
> later, someone's going to write/read something.

Correct, that's why we're discussing to freeze the request queue as well.

> If you want head parking at shutdown, I suggest using hdparm -y. This puts the 
> drive to sleep, which includes spindle spindown and, included, appropriate 
> head parking.

But it suffers from the same fate - as soon as the disk receives a new
request, it will spin up again. So there is no gain, except that just
parking the head without spinning down the spindle can be performed much
faster.

Bye,
	LenZ
- --
- ------------------------------------------------------------------
 Lenz Grimmer <lenz@grimmer.com>                             -o)
 [ICQ: 160767607 | Jabber: LenZGr@jabber.org]                /\\
 http://www.lenzg.org/                                       V_V
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFC1OseSVDhKrJykfIRAnk3AJ9EqLIBprtaYikZCQaRdIpPOrOWiACeMXOC
pwjn2afI737DDzqOKDaEUCA=
=JtxS
-----END PGP SIGNATURE-----

  reply	other threads:[~2005-07-13 10:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-07 13:13 Head parking (was: IBM HDAPS things are looking up) Martin Knoblauch
2005-07-07 13:38 ` Pekka Enberg
2005-07-07 13:47   ` Martin Knoblauch
2005-07-07 14:45   ` Dan Christensen
2005-07-07 16:39   ` Martin Knoblauch
2005-07-07 16:54     ` Alejandro Bonilla
2005-07-07 17:14       ` Martin Knoblauch
2005-07-07 17:34         ` [Hdaps-devel] " Dave Hansen
2005-07-07 18:45           ` Martin Knoblauch
2005-07-07 18:51             ` Erik Mouw
2005-07-07 18:58               ` Martin Knoblauch
2005-07-07 18:59               ` Shawn Starr
2005-07-07 19:00           ` Martin Knoblauch
2005-07-07 19:10         ` Updating hard disk firmware (Was: Re: Head parking) Frank Sorenson
2005-07-13  8:58           ` Updating hard disk firmware & parking hard disk Gijs Hillenius
2005-07-13 10:10             ` Jan Engelhardt
2005-07-13 10:21               ` Lenz Grimmer [this message]
2005-07-13 11:02                 ` [Hdaps-devel] " Jan Engelhardt
2005-07-13 13:11                   ` Paul Slootman
2005-07-13 19:11                     ` Bill Davidsen
2005-07-13 19:10                       ` Paul Slootman
2005-07-13 19:18                       ` Lee Revell
2005-07-13 23:32             ` [Hdaps-devel] " Shawn Starr

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=42D4EB21.1060305@grimmer.com \
    --to=lenz@grimmer.com \
    --cc=frank@tuxrocks.com \
    --cc=gijs@hillenius.net \
    --cc=hdaps-devel@lists.sourceforge.net \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.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