From: Nicolas Dichtel <nicolas.dich...@6wind.com> Date: Thu, 7 May 2015 11:02:46 +0200
> This idea was informally discussed in Ottawa / netdev0.1. The goal is to > ease the use/scalability of netns, from a userland point of view. > Today, users need to open one netlink socket per family and per netns. > Thus, when the number of netns inscreases (for example 5K or more), the > number of sockets needed to manage them grows a lot. > > The goal of this series is to be able to monitor netlink events, for a > specified family, for a set of netns, with only one netlink socket. For > this purpose, a netlink socket option is added: NETLINK_LISTEN_ALL_NSID. > When this option is set on a netlink socket, this socket will receive > netlink notifications from all netns that have a nsid assigned into the > netns where the socket has been opened. > The nsid is sent to userland via an anscillary data. Series applied, thanks Nicolas. -- 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
