Hi , I would like to understand that why the metadata register size is 64-bit? What is the reason of keeping it to this value. I have scenario where are i would like to store more data then i feel that the register value will increase more than 64-bit which will not be applicable in this implementation.
Scenarion : Description : =========================================================== I have a scenario where i would like the processing for the ipsec packet with a specific ip address and vlan to be processed using the metadata register. I have created pipeline processing using 3 flow-tables. Let us say in the first flow table there is a flow entry where i am matching the ipsec header value and storing it in the metadata so i will be picking up the ipaddress of source and destination from the ipsecheader ip addresss field which will be 32-bit and store it in metadata register. Now i move to the second table where i will store the actual ip address another 32-bit as the metadata and then finally the vlan header which is another 32-bit value to match before parsing the packet to the destination . So all iin total i have now 96 bits(32+32+32) value to store. As the openflow standard says that the pipeline processing using the metadata is old data+ new data+ masking. Can anyone explain me how can i achieve this if possible? Also i would like to understand the concept of metadata register value traversal from table to table in pipeline processing. Thanks and Regards, Neel
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
