First, this conversation seems to be more about OpenFlow than nox... I
would suggest if you want more responses, you might consider moving it
to the openflow-discuss mailing list.

Second, the uin32_t actions in switch_features is an array of flags to
describe which actions are *supported* by the switch.  You specify
actions in a flow_mod or packet_out packet, which both have variable
length action payloads.  For example, if you look at struct
ofp_flow_mod, the length of the message, minus the length of the
structure is the number of bytes of actions specified.   To parse
them, read the action header of the first action, look up the length,
and the next action starts that many bytes later.

Let me know if this is not clear, but there are notes in the header
file that also try to explain this.

- Rob
.



On Wed, Jul 22, 2009 at 7:39 AM, puneet gupta<puneetnl...@gmail.com> wrote:
> Hi Ben,
>
> I could do that but in the structure struct ofp_switch_features(Page21 Sec
> 5.3.1), actions (which is of ofp_action_type ), is defined as uint32_t and
> not as an array.
>
> So i can have only one value and not multiple values?
>
> Or are you saying that send ofp_switch_features struct for the same port "n"
> number of times with different actions each time(Don't think anyone would do
> that ???)
>
> Regards,
> Puneet
> On Wed, Jul 22, 2009 at 7:20 PM, Ben Pfaff <b...@nicira.com> wrote:
>>
>> puneet gupta <puneetnl...@gmail.com> writes:
>>
>> > In the doc "openflow-spec-v0 8 9.pdf" , Page 18- Sec 5.2.3, enum
>> > ofp_action_type is defined having values like
>> > OFPAT_OUTPUT,OFPAT_SET_VLAN_VID
>> > etc.
>> >
>> > However, this is just an enum not a bit vec.
>> >
>> > So for a switch that can support multiple actions for a single packet,
>> > how do
>> > i define its action type ?
>>
>> You add multiple actions with one value per action.
>
>
> _______________________________________________
> nox-dev mailing list
> nox-dev@noxrepo.org
> http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
>
>

_______________________________________________
nox-dev mailing list
nox-dev@noxrepo.org
http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org

Reply via email to