linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Xavier <shiningxc@gmail.com>
Cc: linux-ide@vger.kernel.org, Kel Modderman <kel@otaku42.de>
Subject: Re: storage fixup laptop model dependent ?
Date: Tue, 15 Dec 2009 13:39:26 +0900	[thread overview]
Message-ID: <4B2712FE.10905@kernel.org> (raw)
In-Reply-To: <91752840912140429s22d3aa86jd625e4c6411eb125@mail.gmail.com>

Hello,

On 12/14/2009 09:29 PM, Xavier wrote:
>> I am just wondering : does it really matter in which laptop that disk
>> is used ? As laptop disk can be changed/replaced easily, this also
>> sounds strange to me, but there might be a good reason I am missing :)

OEMs sometimes load specialized firmwares to drives and BIOS may
configure APM differently according to drive model, so it kind of
matters.

> Was it the right place for this information ?
> I added the two people who committed to storage-fixup git, just in case.

storage-fixup is at best a stop-gap measure until something better and
more intelligent comes along.  It might be able to serve as
documentation later on too.  I don't think it would be wise to
configure APM to certain value after matching only the drive model.
That's too wide.  A good solution would be...

* Build database of load cycle limits and useable APM values on drive
  models.

* Monitor load cycle count by smart commands and if it continues to
  increase at an excessive rate, warn the user and configure higher
  APM value.

If you replaced the drive yourself, putting hdparm command in one of
boot scripts should do it for now.  :-(

Thanks.

-- 
tejun

  reply	other threads:[~2009-12-15  4:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 13:33 storage fixup laptop model dependent ? Xavier
2009-12-14 12:29 ` Xavier
2009-12-15  4:39   ` Tejun Heo [this message]
2009-12-18 13:22     ` Xavier
2009-12-21  4:34       ` Tejun Heo
2009-12-22  0:43         ` Robert Hancock
2010-01-11  8:11         ` Tejun Heo
2010-02-17 23:30 ` Xavier Chantry

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=4B2712FE.10905@kernel.org \
    --to=tj@kernel.org \
    --cc=kel@otaku42.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=shiningxc@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).