From: Al Viro <v...@zeniv.linux.org.uk> Date: Thu, 2 May 2019 17:32:23 +0100
> it appears that we might take freeing the socket itself to the > RCU-delayed part, along with socket->wq. And doing that has > an interesting benefit - the only reason to do two separate > allocation disappears. I'm pretty sure we looked into RCU freeing the socket in the past but ended up not doing so. I think it had to do with the latency in releasing sock related objects. However, I might be confusing "struct socket" with "struct sock"
