> 4. Have the RCU callback for flow deletion send the Netlink > broadcast message that tells userspace that the flow is gone. > The Netlink client that sent the actual deletion request > would still get a synchronous response, but the broadcast > would be delayed until the flow was really gone. I think > this might be practical, but I don't know the exact > restrictions on RCU callbacks.
Assuming this is possible from the kernel's perspective, what do we do if the netlink broadcast is dropped for some reason? If we get an ENOBUFS, assume that all flows deletions have completed? This isn't particularly satisfying, but is probably so rare it may not matter. Ethan _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
