From: Tejun Heo <tj@kernel.org>
To: starlight@binnacle.cx
Cc: linux-ide@vger.kernel.org
Subject: Re: unexpected downspeed of AHCI controller on Intel Seaburg 5400
Date: Mon, 24 Nov 2008 14:40:17 +0900 [thread overview]
Message-ID: <492A3E41.7020109@kernel.org> (raw)
In-Reply-To: <6.2.5.6.2.20081124002812.01ca7788@binnacle.cx>
starlight@binnacle.cx wrote:
> Thank you for explaining how it works. Have resigned to living
> with 1.5G. A reason exists to run the ES.2s at their full
> sequential 100 Mbytes/sec (800 Mbits/sec), and I had hoped that
> lowering the latency on the link might squeeze a bit more
> performance. But 1.5 is good enough.
Considering general disk operation speed and the parallel operation
achieved using NCQ, I don't think it will make any noticeable difference.
Thanks.
--
tejun
next prev parent reply other threads:[~2008-11-24 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 20:44 unexpected downspeed of AHCI controller on Intel Seaburg 5400 starlight
2008-11-19 2:04 ` Robert Hancock
2008-11-19 2:06 ` starlight
2008-11-24 5:18 ` Tejun Heo
2008-11-24 5:32 ` starlight
2008-11-24 5:40 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-18 20:22 starlight
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=492A3E41.7020109@kernel.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=starlight@binnacle.cx \
/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).