From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 15688] mptsas & poor performance
Date: Sat, 10 Apr 2010 16:58:43 GMT [thread overview]
Message-ID: <201004101658.o3AGwhrZ015188@demeter.kernel.org> (raw)
In-Reply-To: <bug-15688-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=15688
--- Comment #6 from Brian Sullivan <bexamous@gmail.com> 2010-04-10 16:57:26 ---
BTW, I did not look into this as much, but using 3.xx there also seemed to
be a limit of ~600MB/sec between controller & expander. If I put two arrays
on the expander, each array by itself would do almost 500MB/sec in reads,
but together they couldn't break 600MB/sec. I didn't really look into this
further, maybe I was doing something wrong. ~600MB/sec, however, seems like
exactly 1/2 the bandwidth of the minisas cable between controlller &
expander.
On Sat, Apr 10, 2010 at 5:00 AM, <bugzilla-daemon@bugzilla.kernel.org>wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=15688
>
>
>
>
>
> --- Comment #5 from dujun@perabytes.com 2010-04-10 12:00:53 ---
> Hi Andrew & Kashyap,
>
> It seems to me that the 4.22.00.00 driver from lsi is much faster than
> kernel
> 3.xx version driver. We have 16 WD SATA disks connected through lsi sas
> expander to 1068e hba and linux md raid5 using these disks. The system has
> only
> one quad-core E5405 CPU. With the new lsi driver, we get sequential dd
> read
> performance up to 795MB/s and write performance up to 395MB/s which is
> almost
> twice as the kernel 3.xx driver.
>
> We will investigate different hardware setup further and let u know as soon
> as
> possible.
>
> Johnson
>
> --
> Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply other threads:[~2010-04-10 16:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 20:35 [Bug 15688] New: mptsas & poor performance bugzilla-daemon
2010-04-08 10:31 ` [Bug 15688] " bugzilla-daemon
2010-04-08 15:36 ` bugzilla-daemon
2010-04-09 11:49 ` Desai, Kashyap
2010-04-09 11:50 ` bugzilla-daemon
2010-04-10 12:00 ` bugzilla-daemon
2010-04-10 16:58 ` bugzilla-daemon [this message]
2010-04-29 8:36 ` bugzilla-daemon
2010-07-01 7:53 ` bugzilla-daemon
2010-07-01 9:25 ` bugzilla-daemon
2011-03-20 16:03 ` bugzilla-daemon
2012-01-29 21:53 ` bugzilla-daemon
2012-01-30 18:10 ` bugzilla-daemon
2012-01-30 20:27 ` bugzilla-daemon
2012-01-30 20:44 ` bugzilla-daemon
2012-01-30 20:52 ` bugzilla-daemon
2012-01-31 5:06 ` bugzilla-daemon
2012-06-18 20:19 ` bugzilla-daemon
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=201004101658.o3AGwhrZ015188@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 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.