On Fri, 2014-11-14 at 15:03 -0800, Andy Lutomirski wrote: > If the kernel had an API for this, I'd be all for using it.
It would be user land code, not kernel. Why doing a system call when you can avoid it ? ;) Doing it in the kernel would be quite complex actually. In userland, you can even implement this by machine learning. For every connection you made, you get the 4-tuple and INCOMING_CPU, then you store it in a cache. Next time you need to connect to same remote peer, you can lookup in the cache to find a good candidate. It would actually be good if we could do in a single socket verb a bind_and_connect(fd, &source, &destination) -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
