Oliver, I worked on a project and we were doing some experiemntation with
turning off all of the interrupts for about 1 ms in a function called when
an incoming packet was on the wire.
With extensive network traffic, we would eventually get an ugly crash in the
kernel, during some kind of wake routine. I think you shouldn't worry about
YOUR code getting out of control, I think you should worry more about the OS
becoming unstable.
Moral: Don't do it. If you do it, stress test _THE HELL_ out of your app
before it goes public, and if you get any really strange kernel crashes, you
probably know right where to look.
Good luck!
-jeff
>-----Original Message-----
>From: Oliver King-Smith [mailto:[EMAIL PROTECTED]]
>Sent: Wednesday, July 14, 1999 9:31 AM
>To: [EMAIL PROTECTED]
>Subject: Re: Timing and Interupts
>
>
>With regards to question 3. If I were force to turn off
>interrupts to get
>reliable performance are there any rules of thumb that should
>be followed
>to cause minimal impact to the OS?
>
>Or better yet? Is there a reasonable worse case scenario as to
>how long my
>code will be out of control?
