Messages in this thread | | | Subject | Re: Signal driven IO | Date | Wed, 17 Nov 1999 13:12:46 +0000 (GMT) | From | Alan Cox <> |
| |
> completion ports have two features which RT SIGIO doesn't provide. One > is processor affinity; on SMP systems, when a completion port becomes > ready, the system will try to schedule the callback thread on the same > processor which registered the callback originally. The other is thing > which NT does is LIFO ordering when multiple completion ports are to be > scheduled. Both of these strategies are an attempt to avoid cache > misses. I'm not sure how much different these tricks actually make, but
We have cache affinity already. The scheduler does the work for us. There is certainly scope for pulling tricks like when we do I/O involving copies to userspace from networking we switch the cpu that task allegedly last ran on to be the CPU that blasted all the data into memory
- 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/
| |