From: Aaron Lu <aaron.lu@intel.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
Jeff Garzik <jgarzik@pobox.com>, Aaron Lu <aaron.lwe@gmail.com>,
Jack Wang <jack_wang@usish.com>,
Shane Huang <shane.huang@amd.com>,
Oliver Neukum <oliver@neukum.org>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/2] scsi: sd: set ready_to_power_off for scsi disk
Date: Fri, 14 Sep 2012 16:48:31 +0800 [thread overview]
Message-ID: <5052EF5F.3000103@intel.com> (raw)
In-Reply-To: <1347610640.2794.11.camel@dabdike.int.hansenpartnership.com>
On 09/14/2012 04:17 PM, James Bottomley wrote:
>> Just read the SPC-4 spec, in section 5.12.3, it has words like this:
>>
>> Logical units that contain cache memory shall write all cached data to
>> the medium for the logical unit(e.g., as a logical unit would do in
>> response to a SYNCHRONIZE CACHE command as described SBC-3) prior to
>> entering into any power condition that prevents accessing the
>> media(e.g., before a hard drive stops its spindle motor during a change
>> to the standby power condition).
>>
>> So this looks like cache needs to be synced before the device enter
>> standby/stopped power condition. Or do I miss somthing?
>
> Um, no it says the device shall do the sync on its own (as though it
> received a sync cache). That section says the device shall be
> responsible for cache management in the power states.
Oh, I thought it was the host software's responsibility, thanks for the
explanation.
So if we program the device to let it enter standby/stopped power
condition with the start_stop_unit command, do we need to sync the
cache?
Thanks,
Aaron
next prev parent reply other threads:[~2012-09-14 8:48 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 7:40 [PATCH 0/2] Support runtime power off of HDD Aaron Lu
2012-09-13 7:40 ` [PATCH 1/2] scsi: sd: set ready_to_power_off for scsi disk Aaron Lu
2012-09-13 8:14 ` James Bottomley
2012-09-13 8:23 ` Aaron Lu
2012-09-13 8:37 ` James Bottomley
2012-09-13 8:49 ` Aaron Lu
2012-09-13 8:56 ` James Bottomley
2012-09-13 9:07 ` Aaron Lu
2012-09-13 9:26 ` James Bottomley
2012-09-13 10:16 ` Oliver Neukum
2012-09-13 10:51 ` James Bottomley
2012-09-13 12:34 ` Oliver Neukum
2012-09-13 16:24 ` Alan Stern
2012-09-13 20:18 ` Oliver Neukum
2012-09-13 20:46 ` Alan Stern
2012-09-14 6:57 ` Aaron Lu
2012-09-14 8:15 ` James Bottomley
2012-09-14 5:20 ` Aaron Lu
2012-09-14 8:17 ` James Bottomley
2012-09-14 8:48 ` Aaron Lu [this message]
2012-09-14 10:26 ` James Bottomley
2012-09-14 13:54 ` Aaron Lu
2012-09-17 15:01 ` Aaron Lu
2012-09-13 7:40 ` [PATCH 2/2] libata: acpi: set can_power_off for both ODD and HDD Aaron Lu
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=5052EF5F.3000103@intel.com \
--to=aaron.lu@intel.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=aaron.lwe@gmail.com \
--cc=jack_wang@usish.com \
--cc=jgarzik@pobox.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=shane.huang@amd.com \
--cc=stern@rowland.harvard.edu \
/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).