From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PCI DMA Interrupt latency
Date: Tue, 10 Jan 2006 17:59:16 -0600 [thread overview]
Message-ID: <43C44A54.5070702@shaw.ca> (raw)
In-Reply-To: <5trA6-6MD-39@gated-at.bofh.it>
Burkhard Schölpen wrote:
> Hello,
>
> I'm writing a driver for a custom pci card with an FPGA
> (Xilinx Spartan 2 (XC2S150-6) with PCI 32 LogiCore),
> which can act as a pci bus master. The device is designed
> to do DMA transfers with high bandwidth. One task is to
> send image data to a printer which already works quite
> well, but sometimes there are randomly occuring
> problems concerning the timing between two DMA
> transfers. The issue seems to be something like interrupt
> latency in hardware. Measuring some signals with an
> oscilloscope shows, that the delay from generating the
> interrupt, which signals a finished transfer, to the time
> when the interrupt register on the card is reset (i.e. the
> beginning of the ISR) sometimes increases to more
> than 500 microseconds, which is dimensions too high.
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.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-01-11 0:00 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 ` Robert Hancock [this message]
2006-01-11 0:10 ` PCI DMA Interrupt latency Lee Revell
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=43C44A54.5070702@shaw.ca \
--to=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