[ovs-dev] How user actions are translated to kernel actions?
Jarno Rajahalme
jrajahalme at nicira.com
Fri Nov 21 22:30:32 UTC 2014
OpenFlow actions are initially translated by ofproto-dpif-xlate functions. The kernel actions are generated by the various commit_* functions in lib/odp-util.c, called by the xlate functions.
Regards,
Jarno
On Nov 21, 2014, at 2:00 PM, Masoud Moshref Javadi <moshrefj at usc.edu> wrote:
> Where/how are user actions translated to actions that kernel understands?
> Looking at datapath/actions.c, it seems the kernel only understands OVS_ACTION_ATTR_* from netlink messages.
>
> At the userside it seems that ofproto-dpif-xlate.c:xlate_actions__() looks for the rule by calling rule_dpif_lookup, and fills actions in ctx variable. But I cannot find where actions of the rule are extracted and converted to those that kernel understands.
> Is this ofp-actions.c:ofpacts_execute_action_set() or ofproto-dpif-xlate.c:compose_output_action ()?
>
> --
> Masoud Moshref Javadi
> Computer Engineering PhD Candidate
> Ming Hsieh Department of Electrical Engineering
> University of Southern California
>
> _______________________________________________
> dev mailing list
> dev at openvswitch.org
> http://openvswitch.org/mailman/listinfo/dev
More information about the dev
mailing list