Hi, Ben,
>We're always excited to improve the performance of OVS, so I hope you
>will pass along your results.
We did some evaluations on DPDK-based OVS. We use ClassBench[1] to
generate
1K and 10K rules, and also generate synthetic traffic for these rules. We
choose to generate
low loc
ssues.
At 2016-03-20 00:31:53, "Ben Pfaff" wrote:
>It's not a bug.
>
>I think that you should read our research paper from NSDI 2015. It
>explains how OVS megaflows work:
>http://openvswitch.org/support/papers/nsdi2015.pdf
>
>On Sat, Mar 19, 2016 at 05
Hi, I send this email once, no people replied. I am trying to refresh this
email for a reply.
This discontiguous bit mask issue arises in the following case:
I installed two rules,
ovs-ofctl add-flow br0
in_port=1,dl_type=0x0800,nw_src=10.2.10.0/24,nw_proto=6,tcp_dst=0x0050,priority=1,acti
n Fri, Mar 18, 2016 at 05:02:41PM +0800, Peng He wrote:
>> Hi, I send this email once, no people replied. I am trying to refresh this
>> email for a reply.
>> This discontiguous bit mask issue arises in the following case:
>>
>>
>> I installed two rules,
are four bits unset in this case, and the mask
should be 0xF8 (in network byte order), that is the prefix 10.2.0.0/21 that
should be put in the megaflow.
Hope I am clear and please check the code.
Thanks.
At 2016-03-05 07:36:25, "Ben Pfaff" wrote:
>On Fri, Mar 04, 2
Hi,
I installed some rulesets generated by ClassBench (a ruleset benchmark for
generating ACL and FW rules) in Open vSwitch, and I find many megaflow's mask
has
discontiguous bits. Like mask = 0xfc in network byte order. After some code
investigation I find the problem is in the function *
