Oh joyous - you want to play pingpong with the cache across the irq and
task execution side. Other OS's actually schedule stuff aggressively onto
the same CPU to avoid that.
> When you structure things this way, it also tends to minimize the amount of
> driver code requiring that you disable interrupts. No data structures other
> than the semaphore that are accessed from interrupt, so you don't have to
> block interrupts when doing mutual exclusion.
Granted - its _very_ good for hard real time. It isnt so hot for throughput
-
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.tux.org/lkml/