Hello, On Tue, Nov 24, 2015, at 17:25, Florian Westphal wrote: > Its a well-written document, but I don't see how moving the burden of > locking a single logical tcp connection (to prevent threads from > reading a partial record) from userspace to kernel is an improvement. > > If you really have 100 threads and must use a single tcp connection > to multiplex some arbitrarily complex record-format in atomic fashion, > then your requirements suck.
Right, if we are in a datacenter I would probably write a script and use all those IPv6 addresses to set up mappings a la: for each $cpu; do $ip address add 2000::$host:$cpu/64 dev if0 pref_cpu $cpu done where ip-address would also ensure via ntuples that the packets get routed to the correct cpu. Some management layer could then ensure correct usage of all CPUs. This way less cross-cpu traffic is ensured for the TCP synchronization. I only dealt with medium to low busy RPC systems but that would be my first approach. Would something like that make sense? Would the NxM federation overhead between the RPC system kill this approach? This way you could also make use of the TCP PSH flag like Eric described. Bye, Hannes -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
