From: "Moore, Eric Moore" <Eric.Moore@lsil.com>
To: "Chen, Kenneth W" <kenneth.w.chen@intel.com>, linux-scsi@vger.kernel.org
Cc: 'James Bottomley' <James.Bottomley@SteelEye.com>
Subject: Re: mpt fusion driver performance issue in 2.6.14-rc2
Date: Sat, 1 Oct 2005 00:19:56 -0600 [thread overview]
Message-ID: <001a01c5c650$25719050$1b1015ac@ericmoore> (raw)
In-Reply-To: 200510010027.j910Rhg30932@unix-os.sc.intel.com
On Friday, September 30, 2005 6:27 PM, Chen, Kenneth W wrote:
> Chen, Kenneth W wrote on Thursday, September 29, 2005 11:59 AM
>> Something happened in between kernel 2.6.12 and 2.6.14-rc2, where
>> disk performance went 20X slower on the latest release kernel. I
>> suspect it has something to do with the fusion driver. This showed
>> up in the boot log: "mptscsih: ioc0: DV: Release failed." is it
>> significant?
>
> I think the bug is for real, and it is in the mpt fusion driver. I'm
> not an expert of LSI53C1030 host controller, and I won't pretend to be
> one. Though I have data to show what is going on:
>
> There are two threads during driver initialization. One does domain
> validation (mptscsih_domainValidation) and one does host controller
> initialization (mptspi_probe). During 2nd host controller bringup,
> i.e., bringing up ioc1, it temporary disables first channel (ioc0).
> However, DV is in progress on ioc0 in another thread (and possibly
> running on another CPU). The effect of disabling ioc0 during in-
> progress-domain-validation is that it causes all subsequent DV
> commands to fail and resulting lowest possible performance setting
> for almost all disks pending DV.
>
> Here is a fix that I propose: for the period that ioc0 need to be
> disabled for bringing up ioc1, ioc->active is marked with a special
> flag and have DV thread busy wait on that flag. This avoid mptspi_probe
> thread clash into the DV thread causing brain-damage to DV.
>
> With the patch, all disks are up to the performance expectation and it
> also fixed the "mptscsih: ioc0: DV: Release failed" error message.
>
Thanks for you findings into this.
I'm moving across town, and will not be in the office, nor have
internet access for the next couple days. I will look into this when I
return.
Best regards,
Eric Moore
next prev parent reply other threads:[~2005-10-01 6:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B05667366EE6204181EABE9C1B1C0EB50484F7D4@scsmsx401.amr.corp.intel.com>
2005-10-01 0:27 ` mpt fusion driver performance issue in 2.6.14-rc2 Chen, Kenneth W
2005-10-01 6:19 ` Moore, Eric Moore [this message]
2005-10-12 1:10 ` Chen, Kenneth W
2005-10-14 0:07 Moore, Eric Dean
-- strict thread matches above, loose matches on Subject: below --
2005-10-12 20:57 Moore, Eric Dean
2005-10-12 21:05 ` Chen, Kenneth W
2005-09-29 18:59 Chen, Kenneth W
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='001a01c5c650$25719050$1b1015ac@ericmoore' \
--to=eric.moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=kenneth.w.chen@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox