From: jamal <redacted>
Date: Wed, 06 Jun 2007 19:32:46 -0400

On Wed, 2007-06-06 at 15:35 -0700, David Miller wrote:

quoted

With the above for transmit, and having N "struct napi_struct"
instances for MSI-X directed RX queues, we'll have no problem keeping
a 10gbit (or even faster) port completely full with lots of cpu to
spare on multi-core boxes.

RX queues - yes, I can see;  TX queues, it doesnt make sense to put
different rings on different CPUs.

For the locking is makes a ton of sense.

If you have sendmsg() calls going on N cpus, would you rather
they:

1) All queue up to the single netdev->tx_lock

or

2) All take local per-hw-queue locks

to transmit the data they are sending?

I thought this was obvious... guess not :-)