From: Andrew Morton <akpm@linux-foundation.org>
To: linux-scsi@vger.kernel.org, Eric Moore <Eric.Moore@lsi.com>
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org, bexamous@gmail.com
Subject: Re: [Bugme-new] [Bug 15688] New: mptsas & poor performance
Date: Mon, 5 Apr 2010 13:34:51 -0700 [thread overview]
Message-ID: <20100405133451.fb20d65d.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-15688-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
scsi_drivers-other reports don't appear to be coming out on the
linux-scsi list.
On Sat, 3 Apr 2010 21:16:31 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=15688
>
> Summary: mptsas & poor performance
> Product: SCSI Drivers
> Version: 2.5
> Kernel Version: 2.6.34-020634rc1
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: scsi_drivers-other@kernel-bugs.osdl.org
> ReportedBy: bexamous@gmail.com
> Regression: No
>
>
> The mptsas module from LSI's website, v4.18.00.00, performs much better than
> the mptsas module included in the kernel, v3.something.
>
> I'm only comparing sequential writes (dd if=/dev/zero of=zeros bs=1M), but...
>
> 6 drive MD RAID5 with fresh btrfs, writing 10GB of zeros with dd,
> kernel version: <200MB/sec
> LSI's v4.18.00.00: 395MB/sec
>
> Pretty big difference. I've gone back and forth a few times,
> enabling/disabling write cache on the drives, enabling/disabling ioc,
> enabling/disabling filesystem barriers... I can make small changes in
> performance but nothing compares to simply updating to v4.18.00.00.
>
next parent reply other threads:[~2010-04-05 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-15688-10286@https.bugzilla.kernel.org/>
2010-04-05 20:34 ` Andrew Morton [this message]
2010-04-08 9:25 ` [Bugme-new] [Bug 15688] New: mptsas & poor performance Desai, Kashyap
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=20100405133451.fb20d65d.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Eric.Moore@lsi.com \
--cc=bexamous@gmail.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=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.