Hi, We found it’s not ok when controller is set. What’s the difference? Is the variable wc(struct flow_wildcards) modified in function classifier_lookup?
On 2013年12月21日, at 2:57, faicker mo <[email protected]> wrote: > Hi, > > When doing netperf TCP_CC and TCP_CRR with openvswitch-2.0.0 on > CentOS6.3(2.6.32-279.19.1), we found Megaflow which supposed to boost flow > setup rate does not take effect. ovs-dpctl shows many flows that match tcp > source port. > Our flows are setup like this: in_port=20,dl_src=XXXXXX,dl_dst=XXXX > actions=set_field:0xXXXX->tun_id,output:36, it's not necessary to match tcp > source port. > > However, when using actions=normal flow, flows in kernel are indeed setup > like megaflow, that is being wild carded. We are not very familiarly with the > implementation details of kernel datapath, can anyone suggest what's the > mechanism of megaflow and what should we do to utilize megaflow? _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
