On Fri, 2008-22-08 at 03:42 -0700, David Miller wrote: > I had another idea in the back of my head that I wanted to mention. > > The SKB has a hash, and sources set the hash. It doesn't matter > where in the stack it comes from. > > At transmit time, the select queue logic in dev_queue_xmit() will use > the SKB hash if one has been set already. Otherwise it will do the > hashing it does currently. > > So in the simplest case for forwarding, the RX side puts the RSS > hash or whatever into this SKB hash location. > Makes sense. In the case Herbert described, I am assuming that the RSS side could be configured to select a processor statically (MSI or otherwise). And that the hash value will be that of the processorid ego the tx queue selected. > Then, taking things to the next level, protocols set hashes for > locally created packets. And this leads to being able to delete > the simple_tx_hash() code entirely and also we won't have to add > support for every protocol on the planet to that function. :) > Well, conntrack could be useful (as long as you dont make it mandatory) since it already keeps track of flows. When unresolved, one could add it to some default queue. cheers, jamal -- 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
