From: Tejun Heo <tj@kernel.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Jeff Garzik <jeff@garzik.org>,
t.artem@mailcity.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ahci: CAP_SSS and parallel scan
Date: Thu, 06 May 2010 16:44:38 +0200 [thread overview]
Message-ID: <4BE2D5D6.1010705@kernel.org> (raw)
In-Reply-To: <4BE28C4F.9000903@linux.intel.com>
Hello,
On 05/06/2010 11:30 AM, Arjan van de Ven wrote:
> The thing is, SSS means the system requests (well, demands) that we
> don't spin up the disks up in parallel.... which we really really
> ought to honor... Jeff had a very valid point.
Hmmm... yeah but SSS doesn't really demand it. It just says "I can do
staggered spin up". I wish this thing had been implemented in the
form of "stay spin down till necessary (ie. start in standby mode)".
Currently, there's no way to tell whether staggered spin up is needed
or drives are already spun up.
> While today some bioses may spin everything up, that's not going to
> be the case going forward... the industry as a whole is moving away
> from that (slowly but steadily).
Yeah, sure, in the long run maybe but I'm skeptical how useful this is
at this point. Going forward, the right thing to do would be
implementing some sort of token infrastructure so that drivers can
request and hold the token while spinning up a drive so that the
concurrency of spin ups can be controlled.
Jeff, what do you think about lifting the check for now unless there
are known cases where this can cause problems?
Thanks.
--
tejun
next prev parent reply other threads:[~2010-05-06 14:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-06 8:22 ahci: CAP_SSS and parallel scan Tejun Heo
2010-05-06 9:30 ` Arjan van de Ven
2010-05-06 14:44 ` Tejun Heo [this message]
2010-05-06 19:49 ` Jeff Garzik
2010-05-07 5:14 ` Tejun Heo
2010-05-07 21:33 ` Jeff Garzik
2010-05-08 8:40 ` Tejun Heo
2010-05-08 21:53 ` Jeff Garzik
2010-05-06 20:19 ` Mark Lord
2010-05-07 5:16 ` Tejun Heo
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=4BE2D5D6.1010705@kernel.org \
--to=tj@kernel.org \
--cc=arjan@linux.intel.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=t.artem@mailcity.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 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).