Call for performance evaluation: net.isr.direct (fwd)

[Andrew Gallatin]

Poul-Henning Kamp writes:
 > The solution is not faster but less reliable timekeeping, the
 > solution is to move the scheduler(s) away from using time as an
 > approximation of cpu cycles.

So you mean rather than use binuptime() in mi_switch(), use some
per-cpu cycle counter (like rdtsc)?

Heck, why not just use ticks for the scheduler and keep the expensive
timekeeping code out of the critical path altogether?  Does it really
need better than 1ms resolution?

Drew