All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Xavier <shiningxc@gmail.com>
Cc: linux-ide@vger.kernel.org, Kel Modderman <kel@otaku42.de>,
	mzxreary@0pointer.de, Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: storage fixup laptop model dependent ?
Date: Mon, 11 Jan 2010 17:11:46 +0900	[thread overview]
Message-ID: <4B4ADD42.60604@gmail.com> (raw)
In-Reply-To: <4B2EFAE9.3080406@kernel.org>

Hello,

On 12/21/2009 01:34 PM, Tejun Heo wrote:
> (cc'ing Kay and Lennart.  Hello.)
> 
> A proper solution would be....
> 
> * Build database of load cycle limits and useable APM values on drive
>   models.  The former shouldn't be difficult.  Each vendor carries
>   only a few product lines at any given time and publish datasheets on
>   the webpage.  Plus, all the mobile drives I've seen are rated for
>   600,000 cycles.  The latter may be a bit more tricky.  Depending on
>   drive model, certain APM values simply don't work (e.g. 255 means
>   max power by spec but some firmwares wrap the value and recognize it
>   as min power), some values overheats the device and so on.  In most
>   cases the value 254 seems safe tho.  storage-fixup.conf should be
>   useable as the source for useable values, I think.
> 
> * Monitor load cycle count by smart commands and if it continues to
>   increase at an excessive rate (e.g. such that it reduces uptime to
>   under a year), warn the user and configure higher APM value.
> 
> As this problem mostly happens on laptops, I think it's probably best
> to handle this from the new desktop disk management thing so that the
> user can be warned.  Do you think it's feasible to handle this from
> devkit?

Lennart, any thought on this?

Thanks.

-- 
tejun

  parent reply	other threads:[~2010-01-11  8:06 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
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 [this message]
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=4B4ADD42.60604@gmail.com \
    --to=htejun@gmail.com \
    --cc=kay.sievers@vrfy.org \
    --cc=kel@otaku42.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=mzxreary@0pointer.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.