> In compose_output_action__(), the reason for the new test against > OVSP_NONE isn't clear to me. Is this where we end up if a patch port > doesn't have a peer? (How does it get OVSP_NONE?)
Right, all patch ports are initialized with OVSP_NONE. If the patch port has a peer, it will be caught by the patch port implementation code. Otherwise it will fall through and try to output to OVSP_NONE. Ethan _______________________________________________ dev mailing list [email protected] http://openvswitch.org/mailman/listinfo/dev
