public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Rolf Eike Beer <eike@sf-mail.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Rolf Eike Beer <eike-kernel@sf-tec.de>,
	adam radford <aradford@gmail.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@hansenpartnership.com>,
	Chris Wright <chrisw@sous-sol.org>
Subject: Re: [PATCH] Add new driver for LSI 3ware 9750
Date: Thu, 29 Oct 2009 20:14:21 +0100	[thread overview]
Message-ID: <200910292014.28787.eike@sf-mail.de> (raw)
In-Reply-To: <20091023112137.GB19566@parisc-linux.org>

[-- Attachment #1: Type: Text/Plain, Size: 1360 bytes --]

Am Freitag 23 Oktober 2009 13:21:38 schrieb Matthew Wilcox:
> On Wed, Oct 21, 2009 at 05:27:27PM +0200, Rolf Eike Beer wrote:
> > > +	/* Try to enable MSI */
> > > +	if (use_msi && !pci_enable_msi(pdev))
> > > +		set_bit(TW_USING_MSI, &tw_dev->flags);
> > > +
> > > +	/* Now setup the interrupt handler */
> > > +	retval = request_irq(pdev->irq, twl_interrupt, IRQF_SHARED, "3w-sas",
> > >  tw_dev); +	if (retval) {
> > > +		TW_PRINTK(tw_dev->host, TW_DRIVER, 0x1f, "Error requesting IRQ");
> > > +		goto out_remove_host;
> > > +	}
> >
> > If you're using MSI you should not pass IRQF_SHARED here.
> 
> That's not true.  While it is currently the case that each MSI gets its
> own vector, if you have a machine with sufficiently many interrupt sources
> and insufficiently many interrupt vectors, it is possible we'll have to
> share interrupt vectors.  The PCI MSI code does not support this yet,
> but it may have to in the future, and it would be unpleasant to have to
> go through and change all the device drivers.

Sounds reasonable. Anyway I've seen the exact opposite comment from Chris (CC 
added) in his review of VMware's driver (Message-ID: 
<20091013053726.GE17547@sequoia.sous-sol.org> from Mon, 12 Oct 2009 22:37:26 
-0700).

Either way is fine for me, I just would like to have a common agreement on 
that.

Eike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-10-29 19:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-21  0:22 [PATCH] Add new driver for LSI 3ware 9750 adam radford
2009-10-21 15:27 ` Rolf Eike Beer
2009-10-23 11:21   ` Matthew Wilcox
2009-10-29 19:14     ` Rolf Eike Beer [this message]
2009-10-29 20:08       ` James Bottomley
2009-10-30 13:54       ` [PATCH Resend 3/3] pm8001:fix for allocate proper tag for per ccb fix error out and cleanup code jack_wang
2009-10-23 13:53 ` [PATCH] Add new driver for LSI 3ware 9750 Bartlomiej Zolnierkiewicz
2009-11-05 14:45   ` Bartlomiej Zolnierkiewicz

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=200910292014.28787.eike@sf-mail.de \
    --to=eike@sf-mail.de \
    --cc=James.Bottomley@hansenpartnership.com \
    --cc=aradford@gmail.com \
    --cc=chrisw@sous-sol.org \
    --cc=eike-kernel@sf-tec.de \
    --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