From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Date: Mon, 21 Jul 2008 23:22:20 +0800 > On Mon, Jul 21, 2008 at 08:09:01AM -0700, David Miller wrote: > > > > > Actually you've hit it on the head, as an alternative to TX hashing > > > on the packet content, we need to allow TX queue selection based on > > > the current CPU ID. > > > > This we should avoid, it would allow reordering within a flow. > > Not if the RX hashing is flow-based... Can you control the process scheduler and where it decides to run the processing running sendmsg() too? That's the problem. It is totally unwise to do CPU based TX hashing. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
