public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kendrick Hamilton <hamilton@sedsystems.ca>
To: linux-kernel@vger.kernel.org
Subject: Timer Interrupts, please CC hamilton@sedsystems.ca
Date: Mon, 08 Sep 2003 13:11:22 -0600	[thread overview]
Message-ID: <3F5CD45A.2060207@sedsystems.ca> (raw)

Hello,
    Please send/cc responses to hamilton@sedsystems.ca
    We are using a custom modulator card with the Linux 2.2.16 kernel 
running on an IBM e-server (dual 2.8GHz, a lot of RAM). The modulator 
card uses interrupts to send data (the card has a large FIFO and 
interrupts when almost empty). The interrupt service routine re-fills 
the fifo. While it is re-filling the FIFO interrupts are disabled. We 
are noticing horrible clock skew.
    Can you tell me the frequency of timer interrupts used by the linux 
2.2.16 kernel on Intel x86 SMP platform. I want to know how long my 
interrupt service routine can leave the interrupt disabled.
    TIA
Kendrick Hamilton
hamilton@sedsystems.ca



             reply	other threads:[~2003-09-08 19:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 19:11 Kendrick Hamilton [this message]
2003-09-09 22:39 ` Timer Interrupts, please CC hamilton@sedsystems.ca George Anzinger

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=3F5CD45A.2060207@sedsystems.ca \
    --to=hamilton@sedsystems.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