public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Anirban Chakraborty <anirban.chakraborty@qlogic.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"douglas.w.styner@intel.com" <douglas.w.styner@intel.com>
Subject: Re: [PATCH] qla2xxx: Resolved a performance issue in interrupt handler
Date: Tue, 9 Jun 2009 15:47:59 -0600	[thread overview]
Message-ID: <20090609214759.GR3274@parisc-linux.org> (raw)
In-Reply-To: <6FEBF8A9-AA4F-496A-B549-AE5D4275A8A4@qlogic.com>

On Tue, Jun 09, 2009 at 02:46:12PM -0700, Anirban Chakraborty wrote:
>
> On Jun 9, 2009, at 2:43 PM, Matthew Wilcox wrote:
>> While I don't think Doug has MSI-X adapters, a complete patch would  
>> change
>> all request_irq() calls to use IRQF_DISABLED, right?
>
> The above patch takes care of replacing all the IRQF_SHARED flags in irq 
> registrations with IRQF_DISABLED.

Yes ... but even for the MSI-X case, you want the handler to be run with
interrupts disabled, don't you?  If not, why not?

-- 
Matthew Wilcox				Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2009-06-09 21:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-09 18:42 [PATCH] qla2xxx: Resolved a performance issue in interrupt handler Anirban Chakraborty
2009-06-09 19:32 ` James Bottomley
2009-06-09 20:34   ` Anirban Chakraborty
2009-06-09 20:40     ` James Bottomley
2009-06-09 21:28       ` Giridhar Malavali
2009-06-09 21:41         ` Matthew Wilcox
2009-06-09 21:46         ` James Bottomley
2009-06-09 21:40       ` Anirban Chakraborty
2009-06-09 21:43         ` Matthew Wilcox
2009-06-09 21:46           ` Anirban Chakraborty
2009-06-09 21:47             ` Matthew Wilcox [this message]
2009-06-09 22:30               ` Anirban Chakraborty
     [not found]         ` <D7C42C27E6CB1E4D8CBDF2F81EA92A26035402EBA0@azsmsx501.amr.corp.intel.com>
     [not found]           ` <2796FDDF-31EA-44E2-8856-84A22F31A01F@qlogic.com>
2009-06-10 15:52             ` Styner, Douglas W
2009-06-10 16:09               ` Anirban Chakraborty
2009-06-10 16:17                 ` James Bottomley
2009-06-10 16:18                 ` Matthew Wilcox
2009-06-10 18:29                   ` Anirban Chakraborty
2009-06-10 18:32                   ` [PATCH] qla2xxx: Resolved a performance issue in interrupt Andrew Vasquez
2009-06-10 19:10                     ` James Bottomley
2009-06-10 19:48                       ` Matthew Wilcox
2009-06-10 20:55                       ` Anirban Chakraborty
2009-06-12 22:48                         ` Styner, Douglas W
2009-06-12 22:52                         ` [PATCH] qla2xxx: Resolved a performance issue in interrupt - this time with data Styner, Douglas W
2009-06-12 23:32                           ` Anirban Chakraborty
     [not found] <B8134F80-B547-4E04-890A-6B646D2BA3E8@qlogic.com>

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=20090609214759.GR3274@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=anirban.chakraborty@qlogic.com \
    --cc=douglas.w.styner@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