>     I don't understand what is so difficult about simply rate-limiting
>     the code at the proper point -- at the very beginning of the
>     call that the interrupt harvester makes, removing most of the fixed
>     overhead for the case where a system is getting a large number of 
>     interrupts per second?  Why are you going through loops to create
>     complex, sensitive code paths when a simple solution can be plopped 
>     down and will work, SNAP, just like that?

Because I need to make folks other than you happy.

Lots of security minded people what _all_ the interrupt entropy
they can get, and this method gives them that while allowing others
to throttle the harvester back.

Mark Murray
Warning: this .sig is umop ap!sdn

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to