On Thu, 2015-10-08 at 20:42 -0700, Tom Herbert wrote: > On Thu, Oct 8, 2015 at 8:37 AM, Eric Dumazet <eduma...@google.com> wrote: > > As promised in last patch series, we implement a better SO_REUSEPORT > > strategy, based on cpu affinities if selected by the application. > > > > We also moved sk_refcnt out of the cache line containing the lookup > > keys, as it was considerably slowing down smp operations because > > of false sharing. This was simpler than converting listen sockets > > to conventional RCU (to avoid sk_refcnt dirtying) > > > > Could process 6.0 Mpps SYN instead of 4.2 Mpps on my test server. > > > Is this IPv4, IPv6, or some combination of the two ? :-)
IPv4 only (mostly because I was using trafgen and its csumtcp() only deals with IPv4 and I am lazy) I guess IPv6 one might hit some issues before reaching TCP stack, I do not see anything performance related in TCP itself. -- 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
