From: "Laurent Wandrebeck" <l.wandrebeck@gmail.com>
To: adam radford <aradford@gmail.com>
Cc: Tony Battersby <tonyb@cybernetics.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: pci_set_mwi and 3ware controllers
Date: Fri, 23 May 2008 21:56:58 +0200 [thread overview]
Message-ID: <fc593b510805231256l296729dcydbb190aa750b3ac7@mail.gmail.com> (raw)
In-Reply-To: <b1bc6a000805231239i34731c79h3b29fad00b1e8eb1@mail.gmail.com>
2008/5/23 adam radford <aradford@gmail.com>:
> On Fri, May 23, 2008 at 5:33 AM, Laurent Wandrebeck
> <l.wandrebeck@gmail.com> wrote:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=1e6c38cec08f88b0df88a34e80f15492cace74e9
>> patch.
>> I have at work a mobo (with 3ware 9650) that doesn't enable mwi by
>> default, and running CentOS 5.1 x86_64 (2.6.18 based).
>> I can confirm that putting pci_set_mwi just after pci_set_master gives
>
> The 3w-9xxx driver in 2.6.25 already calls 'pci_try_set_mwi(pdev)'.
Agreed. But RHEL/Centos doesn't update "their" kernel as much as the main tree.
And, I'm not really willing to have a much different and less tested
kernel (in RHEL/CetnOS context, that is) as the one provided by
default.
Anyway, I was just willing to let you know that the fix works fine
with others than 9550 controllers ;)
Regards,
Laurent.
prev parent reply other threads:[~2008-05-23 19:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fc593b510805230533lf28171fp24459bf09321500e@mail.gmail.com>
2008-05-23 19:39 ` pci_set_mwi and 3ware controllers adam radford
2008-05-23 19:56 ` Laurent Wandrebeck [this message]
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=fc593b510805231256l296729dcydbb190aa750b3ac7@mail.gmail.com \
--to=l.wandrebeck@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=aradford@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tonyb@cybernetics.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).