On 11 April 2016 at 18:46, pravin shelar <pshe...@ovn.org> wrote: > On Mon, Apr 11, 2016 at 5:58 PM, Ben Pfaff <b...@ovn.org> wrote: >> On Mon, Apr 11, 2016 at 01:14:26PM -0700, pravin shelar wrote: >>> The datapath truncate action should not be associated with output >>> action. It should be general truncate action with truncate length >>> parameter. This way we can apply it to actions other than output. >> >> This may require more care than perhaps you expect. For example, if the >> truncation removes a header, or part of a header, then the extracted >> flow may need to be updated. It might also mean that datapath actions >> to modify fields become invalid. > > There is no need to truncate packet immediately. We can keep the > truncate len in skb_ovs_cb and use it to truncate packet right before > seeing it over port or to user-space up-call.
So, if you have a packet with length 100, then do the following actions: truncate(64),output(1),truncate(100),output(2), then port 1 will see the truncated packet but port 2 will see the full (100 bytes of) packet? _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
