On Thu, 2016-09-22 at 18:14 +0200, Paolo Abeni wrote: > I think that the idea behind using atomic ops directly on > sk_forward_alloc is to avoid adding other fields to the udp_socket. > > If we can add some fields to the udp_sock structure, the schema proposed > in this patch should fit better (modulo bugs ;-), always requiring a > single atomic operation at memory reclaiming time and at memory > allocation time. But do we want any additional atomic to begin with ? Given typical number of UDP sockets on a host, we could reserve/forward alloc at socket creation time, and when SO_RCVBUF is changed. I totally understand that this schem does not work with TCP, because TCP BDP mandates xx MB of buffers per socket, and we really handle millions of TCP sockets per host, But for UDP, most applications are working well with a default limit, and we hardly have more than 1000 UDP sockets. cat /proc/sys/net/core/rmem_default 212992 -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
