mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: jvrao <jvrao@linux.vnet.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	rt-users <linux-rt-users@vger.kernel.org>,
	Mike Anderson <andmike@linux.vnet.ibm.com>,
	"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
	linux-driver@qlogic.com
Subject: Re: Interrupts are being dropped under heavy IO on -rt .
Date: Fri, 10 Apr 2009 23:59:48 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904102357470.21577@localhost.localdomain> (raw)
In-Reply-To: <49DF71CF.7070509@linux.vnet.ibm.com>

On Fri, 10 Apr 2009, jvrao wrote:
> Qlogic driver uses MSI-EDGE interrupts by default.
> 
> On -rt kernel under heavy IO load we observed that the driver missed
> interrupts occasionally.
> 
> Missing interrupts caused spurious mailbox timeouts and path failovers.
> 
> Suspecting MSI interrupts, we disabled MSI and forcing the driver to use APIC
> interrupts (Patch attached).
> 
> With this change, our IO tests ran for extended period of time without any
> issues.
> 
> It would be interesting to see if the MSI infrastructure itself has issues on
> realtime, or it is the combination of qla2xxx/MSI.
> 
> Right now we don't have any setup to test out MSI with other adapters. Hence,
> wondering if anyone faced similar issues.

Hmm. Can we get down to the root cause of that problem instead of
applying a bandaid patch ?

If -rt has problems with MSI edge interrupts then we really need to
figure out why. If the qlogic driver has problems with the different
timings of -rt then we need to fix that one.

Thanks,

	tglx

  reply	other threads:[~2009-04-10 22:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-10 16:20 jvrao
2009-04-10 21:59 ` Thomas Gleixner [this message]
2009-04-15 19:48 ` Andrew Vasquez
2009-04-23 21:38   ` jvrao
2009-04-27  5:13     ` jvrao

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=alpine.LFD.2.00.0904102357470.21577@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=andmike@linux.vnet.ibm.com \
    --cc=jvrao@linux.vnet.ibm.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-driver@qlogic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@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

all inboxes | Powered by JetHome®