Matthew Dillon wrote: > Interrupt threads have 'grown' on me. I like them. > But I come from an embedded world where switching threads > costs no more then a procedure call. The way I figure it, > we will eventually be able to make -current's scheduler > efficient enough such that the overhead of switching to > an interrupt thread becomes a non-issue, and they take care > of the big problem we've always had with interrupts under > SMP... managing interrupts in an SMP environment.
Don't get me wrong... 15% is heavy overhead, but I expect that, over time, that performance gap will at least narrow, if not disappear, if hyperthreading becomes domething other than a parketing buzzword. > I am somewhat partial to the interrupt context stealing > idea too, though I'm not sure if the added complexity is > worth it (time may be better spent improving the scheduler). I like context stealing, too. I've liked it ever since I first saw it in Windows 95 back in 1996; it's been common practice in the Windows world for a long time. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
