We try to implement the minimum interface that we can in the kernel. Usually the TTL doesn't change across a flow, so matching on a particular TTL value and setting a new value isn't a problem. Plus, it allows us flexibility to stack multiple OpenFlow decrements (useful for logical routers, for example) to become a single modify action in the kernel.
Is there a particular use-case that requires decrement? --Justin > On Jun 24, 2019, at 5:06 PM, Sagar A <[email protected]> wrote: > > Hello, > > I see that there is an action OFPACT_DEC_TTL in user space, but not in kernel > space for OVS. Is there a reason why kernel space action is not implemented? > If one has to implement the kernel space action OFPACT_DEC_TTL, what will be > the approach? The reason I want to have kernel space action OFPACT_DEC_TTL is > that to avoid 'ttl' as the match condition in flow. > > Thank you. > _______________________________________________ > discuss mailing list > [email protected] > https://mail.openvswitch.org/mailman/listinfo/ovs-discuss _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
