From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
t.artem@mailcity.com,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: ahci: CAP_SSS and parallel scan
Date: Fri, 07 May 2010 07:14:14 +0200 [thread overview]
Message-ID: <4BE3A1A6.1040106@kernel.org> (raw)
In-Reply-To: <4BE31D57.6020400@garzik.org>
Hello,
On 05/06/2010 09:49 PM, Jeff Garzik wrote:
> The problem being... that we are honoring SSS bit, and thus thing are
> slower? :) I don't see any reason to change that, seeing as how people
> may be using it to avoid power spikes.
>
> I agree there's no way to tell whether SSS is needed, but we cannot
> ignore SSS on that basis alone. We should avoid making the assumption
> that BIOS w/ SSS bit has already spun up all drives regardless.
It's just that the usefulness seems very limited at this point so it
might be better idea to flip the default behavior and let people opt
in for SSS. The problem is compounded by the complete serial behavior
we end up with and on some machines large number of ahci ports. I
don't care much about boot time all that much but as that seems to be
a hot issue on desktops too these days.
Thanks.
--
tejun
next prev parent reply other threads:[~2010-05-07 5:14 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
2010-05-06 19:49 ` Jeff Garzik
2010-05-07 5:14 ` Tejun Heo [this message]
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=4BE3A1A6.1040106@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).