On Wed, Apr 1, 2015 at 10:14 PM, Neil McKee <neil.mc...@inmon.com> wrote: > I've been looking at filling in the sFlow structures to report on tunnel > encap and other transformations. sFlow sampling is best done on ingress > only, so I can't use the egress-sampling action that the IPFIX > implementation uses to get the tunnel info. So how should I look up the > list of actions for a flow when an sFlow sample appears in > ofproto-dpif-upcall.c:process_upcall()? There is not enough room for all > the fields we need in the (8-byte) userdata-cookie that goes with the > compiled actions into the kernel and is passed back on the upcall. But it > should be possible to look up the whole list of actions in user-space when > we process the upcall. Here are some possible ways. Please comment:
If you're trying to get the outer tunnel information for both ingress and where a packet will eventually egress, I don't think that having the list of kernel actions is sufficient. It can tell you some things, like the tunnel type and destination IP address but not UDP source port, for example. Can you explain why sampling must be done at the beginning of the pipeline? Is it just trying to avoid other transforms like vlan tags? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
