Hi Su, I don't believe your rewriting of flowmod is correct exactly. You are doing a union rather than an intersection in my opinion. It should be more like this: Re-FlowMod1: In_port=1; (FlowMod1 intersects with Rule1) Re-FlowMod2: No Match; (Since FlowMod1 has a port number which cannot be intersected with ip-address rule2 especially when no port num is mentioned in rule2 ) Re-FlowMod3: No Match; (same case as above) Re-FlowMod4: dl_src=yyy,dl_dst=yyy; (FlowMod2 intersects with Rule2 - here we get the partial map of whatever ip addresses are intersected in between) rule 3 only applies to IP address because ip field can be partially mapped due to its subnetting ability. Hope this clears!
Cheers Sumanth On Mon, May 6, 2013 at 6:31 AM, Su <sujz.b...@qq.com> wrote: > Hi,all > > I am recently puzzled over intersects computation in flowvisor-1.0, the > following passages is taken from comments of function > FlowSpaceRuleStore::intersect(long dpid, FVMatch match): > > /*** > 3. We have a potential partial match: 3.1 The field and the flow rule > field do not overlap, return no match. 3.2 The fields overlap, return the > smallest possible intersection of the two. > Currently rule 3 only applies to IP address, but this could change in the > future. > ***/ > > According to this rule, If the following FlowSpaceRules exists and two > FlowMods comes from some controller sequentially: > FlowSpaceRules: > Rule1: In_port = 1; > Rule2: Ipv4_src=xxx,Ipv4_dst=xxx; > FlowMods: > FlowMod1: In_port=1; > FlowMod2: dl_src=xxx,dl_dst=xxx; > After FlowVisor intersects pairwisely, the FlowMod messages should be > rewritten with: > Re-FlowMod1: In_port=1; (FlowMod1 intersects with Rule1) > Re-FlowMod2: In_port=1,Ipv4_src=xxx,Ipv4_dst=xxx; (FlowMod1 intersects > with Rule2) > Re-FlowMod3: dl_src=xxx,dl_dst=xxx; (FlowMod2 intersects with Rule1) > Re-FlowMod4: dl_src=xxx,dl_dst=xxx,Ipv4_src=xxx,Ipv4_dst=xxx; (FlowMod2 > intersects with Rule2) > > FlowMod Re-FlowMod3 is not like what it preconceived to be, so I don't > understand the reason why rule 3 only applies to IP address, is there > anything special on this field or any other reason? > > Thanks. > > _______________________________________________ > openflow-discuss mailing list > openflow-discuss@lists.stanford.edu > https://mailman.stanford.edu/mailman/listinfo/openflow-discuss > >
_______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
