linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yani Ioannou <yani.ioannou@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Jens Axboe <axboe@suse.de>,
	Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
	Jon Escombe <lists@dresco.co.uk>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Alejandro Bonilla Beeche <abonilla@linuxwireless.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	hdaps devel <hdaps-devel@lists.sourceforge.net>,
	linux-ide@vger.kernel.org
Subject: Re: PATCH: ide: ide-disk freeze support for hdaps
Date: Sun, 28 Aug 2005 01:30:12 -0400	[thread overview]
Message-ID: <253818670508272230540fa9dd@mail.gmail.com> (raw)
In-Reply-To: <20050827123408.GD1109@openzaurus.ucw.cz>

Hi Pavel,

On 8/27/05, Pavel Machek <pavel@suse.cz> wrote: 
> Well, with my power-managment hat on:
> 
> we probably want "freeze" functionality to be generic; it makes sense
> for other devices, too.
> 
> "My battery is so low I can not use wifi any more" => userspace
> freezes wifi.
> 
> Now, having this kind of timeout in all the cases looks pretty ugly to my eyes.

Thing is the freeze attribute hasn't got much to do with power
management, this is just to freeze the queue, and park the drive head
ASAP (preferably with the unload immediate command supported by new
drives) in order to protect the drive in an impact. Unload immediate
doesn't even stop spinning the drive, so little power is saved.

Maybe a suspend attribute would be a good idea for something along the
lines of what you have in mind? A enable/disable attribute would
definitely make sense for that application.

I suppose renaming the attribute to "ramming_speed" or
"brace_for_impact", might make the purpose more clear ;).

Thanks,
Yani

      reply	other threads:[~2005-08-28  5:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-25 14:08 PATCH: ide: ide-disk freeze support for hdaps Yani Ioannou
2005-08-25 15:59 ` Bartlomiej Zolnierkiewicz
     [not found]   ` <58cb370e0508250859701ea571-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2005-08-26  5:04     ` Yani Ioannou
2005-08-26  6:55       ` Jens Axboe
2005-08-27 12:34         ` Pavel Machek
2005-08-28  5:30           ` Yani Ioannou [this message]

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=253818670508272230540fa9dd@mail.gmail.com \
    --to=yani.ioannou@gmail.com \
    --cc=abonilla@linuxwireless.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=axboe@suse.de \
    --cc=bzolnier@gmail.com \
    --cc=hdaps-devel@lists.sourceforge.net \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).