public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jeff@garzik.org>
Subject: Re: [PATCH] Make libata not powerdown drivers on PM_EVENT_FREEZE.
Date: Thu, 23 Mar 2006 22:16:03 +1000	[thread overview]
Message-ID: <200603232216.08538.ncunningham@cyclades.com> (raw)
In-Reply-To: <20060323040649.3a6c96f1.akpm@osdl.org>

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

Hi.

On Thursday 23 March 2006 22:06, Andrew Morton wrote:
> Nigel Cunningham <ncunningham@cyclades.com> wrote:
> > At the moment libata doesn't pass pm_message_t down ata_device_suspend.
> >  This causes drives to be powered down when we just want a freeze,
> >  causing unnecessary wear and tear. This patch gets pm_message_t passed
> >  down so that it can be used to determine whether to power down the
> >  drive.
>
> Does this explain http://bugzilla.kernel.org/show_bug.cgi?id=6264 ?

Yes, it does.

> This might be 2.6.16.1 material - how irritating is it?

Very. It extends the time to write the image, but as mentioned above, I'm more 
concerned by the fact that (assuming I understand correctly), it's using up 
the limited number of power cycles a drive can handle.

Regards,

Nigel

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-03-23 12:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-23 11:51 [PATCH] Make libata not powerdown drivers on PM_EVENT_FREEZE Nigel Cunningham
2006-03-23 12:06 ` Andrew Morton
2006-03-22 23:26   ` Pavel Machek
2006-03-23 12:16   ` Nigel Cunningham [this message]
2006-03-23 13:09 ` Jens Axboe
2006-03-23 13:20   ` Nigel Cunningham
2006-03-23 13:22   ` Nigel Cunningham
2006-03-23 13:52     ` Jeff Garzik
2006-03-23 21:01       ` Nigel Cunningham
2006-03-23 22:45         ` Mark Lord

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=200603232216.08538.ncunningham@cyclades.com \
    --to=ncunningham@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=jeff@garzik.org \
    --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