On Thu, Feb 18, 2016 at 3:03 PM, Florian Westphal <f...@strlen.de> wrote: > As discussed during netconf 2016 in Seville, this series removes > CONFIG_NETLINK_MMAP.
Sorry for hopping in so^Wtoo late. I always thought mmaped netlink is the way to go for userspace packet processing. Sure, the problems you state are real but that the whole concept is now thrown away kind of surprises me. > Close to three years after it was merged it has retained several problems > that do not appear to be fixable. > > No official netfilter libmnl release contains support for mmap backed netlink > sockets. No openvswitch release makes use of it either. > > To use the mmap interface, userspace not only has to probe for mmap netlink > support, it also has to implement a recv/socket receive path in order to > handle messages that exceed the size of an rx ring element > (NL_MMAP_STATUS_COPY). > > So if there are odd programs out there that attempt to use MMAP netlink > they should continue to work as they already need a socket based code path > to work properly. > > The actual revert (first patch) has a list of problems. > The followup patches remove a couple of helpers that are no longer needed > after the revert. > > I did a few tests with mmap vs. socket based interface on a 4.4 based > kernel on an i7-4790 box and there are no performance advantages: Did you also test smaller devices? i.e. stuff one would use for cheap routers. -- Thanks, //richard
