linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elias Oltmanns <eo@nebensachen.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Tejun Heo <tj@kernel.org>,
	Shem Multinymous <multinymous@gmail.com>,
	Thomas Renninger <trenn@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Laptop shock detection and harddisk protection
Date: Wed, 17 Sep 2008 17:21:01 +0200	[thread overview]
Message-ID: <87d4j2ol2a.fsf@denkblock.local> (raw)
In-Reply-To: <20080817195103.GD4043@ucw.cz> (Pavel Machek's message of "Sun, 17 Aug 2008 21:51:03 +0200")

Pavel Machek <pavel@suse.cz> wrote:
> Hi!
>
>> Short of a satisfying proposition regarding the questions raised, I just
>> want to add two things that would be nice to solve in the future one way
>> or another and should perhaps be taken into consideration from the
>> beginning:
>> 
>> 1. Disable polling completely when it isn't required: once the hd has
>>    spun down, there is no need to keep polling the sensors at all. Only
>>    when the first request requiring the hd to spin up arrives, the
>>    kernel needs to hold back for a short while to gather enough data
>>    from the sensors, so shock protection is up and running again.
>
> hdparm can already tell if disk is spinning or not. As userland is
> polling, already, that may be enough?

Yes, I know it *is* possible, I just think it may not be completely
trivial to get it right. The only way I can think of, right now, is some
sort of polling in the hdparm way, i.e. issuing a ATA_CMD_CHK_POWER from
time to time. The question is how we are to decide when and how often we
should poll for the current power state of the HD.

>
>> 2. Make shock protection interact nicely with suspend operations:
>>    currently, we are out of luck if anything should happen after
>>    processes have been frozen. This is particularly unfortunatel in the
>>    case of s2disk.
>
> I'd say that s2disk is similar to early boot... no protection there. 

Well, this is true for resume. However, I can't help thinking that we
may do better than that until the disk spins down, particularly while
writing the image to disk.

Regards,

Elias

  reply	other threads:[~2008-09-17 15:21 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-10 16:59 Laptop shock detection and harddisk protection Tejun Heo
2008-09-10 19:43 ` Renato S. Yamane
2008-09-11 10:26 ` Austin Zhang
2008-09-11 11:18   ` Tejun Heo
2008-09-11 16:08 ` Shem Multinymous
2008-09-11 16:34   ` Tejun Heo
2008-08-17 19:48     ` Pavel Machek
2008-09-11 20:00     ` Elias Oltmanns
2008-08-17 19:51       ` Pavel Machek
2008-09-17 15:21         ` Elias Oltmanns [this message]
2008-09-17 19:36           ` Shem Multinymous
2008-09-11 20:25     ` Shem Multinymous
2008-08-17 19:30       ` Pavel Machek
2008-09-11 23:35       ` Tejun Heo
2008-09-12 16:59         ` Greg KH
2008-08-17 19:45           ` Pavel Machek
2008-09-17 18:04             ` Greg KH
2008-09-18 11:18               ` Pavel Machek
2008-09-19  9:03                 ` Thomas Renninger
2008-09-24  5:14                   ` Greg KH
2008-10-07 20:40                     ` Pavel Machek
2008-10-07 21:19                       ` Greg KH
2008-10-07 21:40                         ` Pavel Machek
2008-10-07 22:03                           ` Greg KH
2008-10-07 23:03                             ` Pavel Machek
2008-10-07 22:55                         ` Shem Multinymous
2008-09-15  8:29           ` Tejun Heo
2008-09-15 18:09             ` Shem Multinymous
2008-09-15 20:10               ` Tejun Heo
2008-09-14  4:41       ` Jeremy Fitzhardinge
2008-09-11 23:36     ` Henrique de Moraes Holschuh
     [not found] <baBmH-48R-17@gated-at.bofh.it>
2008-09-12 13:28 ` Bodo Eggert

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=87d4j2ol2a.fsf@denkblock.local \
    --to=eo@nebensachen.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=multinymous@gmail.com \
    --cc=pavel@suse.cz \
    --cc=tj@kernel.org \
    --cc=trenn@suse.de \
    /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).