public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: adam radford <aradford@gmail.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-pci@vger.kernel.org
Subject: Re: [PATCH 1/1] 3ware add MSI support
Date: Wed, 23 Jul 2008 07:47:09 -0400	[thread overview]
Message-ID: <1216813629.3557.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20080723014745.GH7337@parisc-linux.org>

On Tue, 2008-07-22 at 19:47 -0600, Matthew Wilcox wrote:
> On Tue, Jul 22, 2008 at 04:36:32PM -0700, adam radford wrote:
> > This patch for the 3w-9xxx scsi driver applies on top of the
> > BKL-pushdown changes in -git9.
> > 
> > This patch does the following:
> > 
> > - Increase max AENs drained to 256.
> > - Add MSI support and "use_msi" module parameter.
> > - Fix bug in twa_get_param() on 4GB+.
> > - Use pci_resource_len() for ioremap().
> 
> Is there a reason you default use_msi to off?  I would have thought
> you'd want to enable it as widely as possible.

Hardly ... just look at our LSI fiasco with globally enabling them.

Right at the moment, due to motherboard bugs, it looks like global
enabling of MSI by default would produce a significant increase in "my
system doesn't boot" type bugs.

I asked Jesse if we could actually get better recognition of
motherboards with MSI problems in pci/quirks.c to forestall some of
this, but it seems to be a hard problem.  I've cc'd the PCI list in case
they have better suggestions.

James

  reply	other threads:[~2008-07-23 11:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 23:36 [PATCH 1/1] 3ware add MSI support adam radford
2008-07-22 23:47 ` adam radford
2008-07-23  1:47 ` Matthew Wilcox
2008-07-23 11:47   ` James Bottomley [this message]
2008-07-23 11:59     ` Boaz Harrosh
2008-07-23 12:05       ` James Bottomley
2008-07-24 14:27         ` Matthew Wilcox
2008-07-23  5:29 ` Rolf Eike Beer

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=1216813629.3557.3.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=aradford@gmail.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=matthew@wil.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