public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: "Schaefer Dr, Frank-Rene ()" <fschaef9@visteon.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interrupt Latencies
Date: Tue, 22 Feb 2011 13:33:57 +0100	[thread overview]
Message-ID: <4D63AD35.6050808@ladisch.de> (raw)
In-Reply-To: <060E4307CE6CA14BB4F7B4A25ECA052904B73AD1@VEUMBV03.vistcorp.ad.visteon.com>

Schaefer Dr, Frank-Rene wrote:
> Having read "Moving interrupts to threads" at
> 
>            http://lwn.net/Articles/302043/
> 
> I expected to reduce interrupt latency during a SPI
> communication by handling the transmit-receive in a
> 'quick_check_handler' using
> 
>            request_threaded_irq(...);
> 
> However, the difference in latency to "request_irq(...)"
> is not measurable.

Threaded interrupts reduce the latency for _other_ interrupts because
most of the code has been moved into the thread.  Without threaded
interrupts, the same could would be in the actual interrupt handler
(the equivalent of the quick check handler).

> It is totally incomprehensible to me why the 'quick_check_handler'
> must have a latency of 60us at min. (that are many thousand
> instructions).

The sytem's interrupt handling and the I/O accesses aren't fast.
Furthermore, waking the CPU up, or changing its frequency, can be quite
slow (but I don't know how much in the case of your Atom).  You could
try reducing the interrupt latency by not letting the CPU get idle but
executing some low-priority busy loop.


Regards,
Clemens

  reply	other threads:[~2011-02-22 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-22  9:35 Interrupt Latencies Schaefer Dr, Frank-Rene ()
2011-02-22 12:33 ` Clemens Ladisch [this message]
2011-02-24  8:01   ` Schaefer Dr, Frank-Rene ()
2011-02-24 12:18     ` Thomas Gleixner
2011-02-22 14:39 ` Thomas Gleixner
2011-02-22 16:10   ` Schaefer Dr, Frank-Rene ()
2011-02-22 17:17     ` Thomas Gleixner

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=4D63AD35.6050808@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=fschaef9@visteon.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