From: Lee Revell <rlrevell@joe-job.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI DMA Interrupt latency
Date: Tue, 10 Jan 2006 19:10:36 -0500 [thread overview]
Message-ID: <1136938237.2007.110.camel@mindpipe> (raw)
In-Reply-To: <43C44A54.5070702@shaw.ca>
On Tue, 2006-01-10 at 17:59 -0600, Robert Hancock wrote:
> Most likely some driver is disabling interrupts for that period, which
> is really longer than it should be. However, if your card/driver require
> such tight interrupt latency to function correctly, that seems too
> fragile and may not be reliable. Some kind of ringbuffer arrangement
> would likely work better, so that the interrupt does not have to be
> serviced so soon.
>
You can easily tell if this is the case by applying these patches:
http://people.redhat.com/mingo/latency-tracing-patches/latency-tracing-patches-2.6.15-rc7.tar.gz
It says -rc7 but they apply cleanly and work with 2.6.15 final.
Lee
next prev parent reply other threads:[~2006-01-11 0:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5trA6-6MD-39@gated-at.bofh.it>
2006-01-10 23:59 ` PCI DMA Interrupt latency Robert Hancock
2006-01-11 0:10 ` Lee Revell [this message]
2006-01-10 13:18 Burkhard Schölpen
2006-01-10 15:31 ` Paul Fulghum
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=1136938237.2007.110.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@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