From: Tim Small <tim@buttersideup.com>
To: linux-ide@vger.kernel.org
Cc: kristen.c.accardi@intel.com
Subject: AHCI link power management and surprise hotplug
Date: Thu, 19 Mar 2009 11:03:37 +0000 [thread overview]
Message-ID: <49C22689.9050005@buttersideup.com> (raw)
Hello,
I've been configuring SATA link power management
(Documentation/scsi/link_power_management_policy.txt) on servers which
use software RAID for a while, but I happened to come across this in the
ICH9 datasheet:
"
For reliable device removal notification while in AHCI operation without
the use of interlock switches (surprise removal), interface power
management should be disabled for the associated port. See Section 7.3.1
of the AHCI Specification for more information.
"
Is this actually an issue from a libata point of view? Do I need to
ensure that link power management is disabled prior to hot-removal, and
if so, I suppose link_power_management_policy.txt should be updated to
reflect this...
On a related topic, is there any way to do anything other than
"surprise" removal with libata? It'd be nice to put a drive to sleep
(e.g. with "hdparm -Y"), and ensure that nothing comes along and causes
the drive to be reset and spin the drive attached to that SATA port back
up prior to a removal and reinsertion.
I'm assuming that physically unplugging a non-spinning drive is
preferable to unplugging a spinning one from a drive longevity point of
view (I use SATA drives as removable backup medium in some cases).
Cheers,
Tim.
next reply other threads:[~2009-03-19 11:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 11:03 Tim Small [this message]
2009-03-19 18:06 ` AHCI link power management and surprise hotplug Jeff Garzik
2009-03-20 1:56 ` Tejun Heo
2009-03-20 17:42 ` Kristen Carlson Accardi
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=49C22689.9050005@buttersideup.com \
--to=tim@buttersideup.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@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;
as well as URLs for NNTP newsgroup(s).