From: Matthew Wilcox <matthew@wil.cx>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: "Rengarajan, Narayanan (STSD)" <narayanan.rengarajan@hp.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH 1/1] : Spinning up disk is observed on standby paths until timeout, resulting in longer path restoration time.
Date: Fri, 20 Feb 2009 10:04:32 -0700 [thread overview]
Message-ID: <20090220170431.GW16841@parisc-linux.org> (raw)
In-Reply-To: <1235147048.9025.9.camel@localhost.localdomain>
On Fri, Feb 20, 2009 at 04:24:08PM +0000, James Bottomley wrote:
> I think the point is that it's a transition: Once it comes out of it we
> either get access or we don't, so it's worth waiting to see what
> happens.
I agree. If we knew that it could only be transitioning to inactive, we
could skip it. This state probably only gets returned once in a blue
moon anyway.
> > I don't know what 'Enable Spinup' is for -- maybe Doug knows? Sending a
> > START_STOP to the device might be exactly what they intend for us to do.
> > Under a 'First, Do No Harm' theory, perhaps we should leave well enough
> > alone and just add Standby and Unavailable?
>
> As I said, it's a SAS power management command related condition: The
> drive is limited to consuming a certain level of power and that's not
> enough to spin up, so it won't spin up regardless of how many start unit
> commands it gets sent until the power management control is changed to
> allow it to consume enough power for the spinup. I think it's ignorable
> for now ... it probably means that when power management is added we
> need to get the transport classes involved to send the appropriate sas
> pm command.
Looking at SAS2r14, I see that NOTIFY (ENABLE SPINUP) is a primitive,
not a command. If the SAS device is attached through an expander, I
don't think we have a way to send that primitive to the device. We must
wait for the expander to send it. If it's sirectly-connected, the
initiator port is supposed to send it. Presumably this is handled
either by firmware on the HBA or by the HBA driver; either way, we don't
seem to have a way today to get the HBA to send this primitive.
I think our current behaviour is correct for this command, so the patch
here: http://marc.info/?l=linux-scsi&m=123513805527153&w=2 is correct.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2009-02-20 17:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 11:14 [PATCH 1/1] : Spinning up disk is observed on standby paths until timeout, resulting in longer path restoration time Rengarajan, Narayanan (STSD)
2009-02-20 15:36 ` James Bottomley
2009-02-20 15:52 ` Matthew Wilcox
2009-02-20 16:03 ` James Bottomley
2009-02-20 16:13 ` Matthew Wilcox
2009-02-20 16:24 ` James Bottomley
2009-02-20 17:04 ` Matthew Wilcox [this message]
2009-02-23 11:48 ` Rengarajan, Narayanan (STSD)
2009-02-23 14:52 ` James Bottomley
2009-02-28 21:26 ` Matthew Wilcox
2009-02-28 23:56 ` James Bottomley
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=20090220170431.GW16841@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=narayanan.rengarajan@hp.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.