hmp at backplane.com
Thu Dec 1 06:14:34 PST 2005
Alfredo Beaumont Sainz wrote:
And what about using CPUs to both RX and TX? That is, bound a packet to a
CPU to both RX and TX?
I am not sure about binding packets to CPUs, but binding by protocol
families would be quite nice I think. Starting by binding specific
IRQs to certain set of CPUs would be much better way to get there since
it would go well with our cpu-locality concept, starting from the
interrupt and right all the way up to a process.
ithread_irq11 -> netisr_cpu1 -> tcpthread_cpu1 -> process on cpu1
hmp at dragonflybsd.org
More information about the Users