From: SA <bullet.train@ntlworld.com>
To: linux-kernel@vger.kernel.org
Subject: interrupt latency k2.4 / i386?
Date: Fri, 7 Feb 2003 18:47:36 +0000 [thread overview]
Message-ID: <200302071847.36646.bullet.train@ntlworld.com> (raw)
Dear list,
What latency should I expect for hardware interrupts under k2.4 / i386 ?
ie how long should it take between the hardware signalling the interrupt and
the interrupt handler being called?
I am wrting a driver which pace IO with interrupts, generating one interrupt
for after every transfer is done. Looking at the hardware schematics the
interrupts should occur virtually instantly after each transfer but the
driver is waiting ~1ms/ interrupt.
I can use polling instead with busy waits but this seems a bit wasteful.
My interrupt is shared with my graphics card using the non-GPL nvidia driver -
could this be responsible for the delay (any experience with this)?
cat /proc/interrupts
.....
10: 3028 XT-PIC eth0, VIA 82C686A
11: 1117037 XT-PIC nvidia, PI stage <-- my driver
12: 14776 XT-PIC usb-uhci, usb-uhci
.....
Thanks SA
next reply other threads:[~2003-02-07 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 18:47 SA [this message]
2003-02-07 19:08 ` interrupt latency k2.4 / i386? Richard B. Johnson
2003-02-07 19:10 ` uaca
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=200302071847.36646.bullet.train@ntlworld.com \
--to=bullet.train@ntlworld.com \
--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;
as well as URLs for NNTP newsgroup(s).