lkml.org 
[lkml]   [1998]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: interrupt latency


On Wed, 12 Aug 1998, Chris Wedgwood wrote:
>
> With the offset of 32, things work as expected and I am able to
> `generate interrupts'. Cool bananas.
>
> It means the guts of what I wanted to do will now have to be done in
> the module which means the interrupt times are going to be ring 0 ->
> ring 0 -> ring 0, instead of ring 3 -> ring 0 -> ring3, are the
> timings likely to be vastly different?

Different? Yes. "Vastly different"? Probably not.

However, usually when people are interested in interrupt latency, they
aren't so much interested in how long an interrupt takes to dispatch, but
how long interrupts may be disabled by whatever code that needs to do some
critical region or whatever.

And that is never going to be tested by a software interrupt. The whole
point of that kind of interrupt latency is to see how quickly the OS can
respond to an _unexpected_ and asynchronous thing.

Linus


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:1.939 / U:0.356 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site