> > I thought of creating one "dummy netdev" per function which will represent
> > each function in open vswitch. These ports can be treated like logical
> > connection to the functions. Whenever there is flow-miss in the device, it
> will
> > punt the packet to the linux kernel via respective "dum
> > That said, my working assumptions are:
> >
> > * That Open vSwitch may manage flow offloads from user-space. This is as
> > opposed to them being transparently handled in the datapath. This does
> > not preclude the existence of transparent offloading in the datapath.
> > But rather limit
> >> /**
> >> * enum ovs_action_attr - Action types.
> >> *
> >> @@ -633,6 +642,10 @@ enum ovs_action_attr {
> >> * data immediately followed by a
> mask.
> >> * The data must be zero for the
> unmasked
> >>
> Following series adds support for tunneling entirely in userspace.
> Even though this is targeted for DPDK based device, this should
> work on any platform that support netdev datapath.
>
> To make tunneling work it need special configuration, There is
> README-native-tunneling file which has de
