On Fri, May 26, 2017 at 7:50 PM, 爬山虎 <[email protected]> wrote: > > > I have saw this patch at "https://patchwork.ozlabs.org/patch/731701/";. We > have build and run at our centos-7.10 OS. > > 1) But i and my colleague don't know how to use the , can you give some > example about the command line operation. Some commands as comments in the > patch are confusing .
There is a test in dpif-netdev.at titled "meters" that shows how meters are configured and used. You may find it useful. > > 2) I still believe that one meter with multiple band is not a good idea. > It's not just let work to be more complicated, but also hard to test . Just > think, we user iperf tools to test the rate of network . If one meter with > one band , it's easy to tell tester , the burst and limit values is just > your set . But if one meter with tow or more band, it's not easy to explain > to the tester . We should tell tester the speed limit results depend on the > speed of the network itself . If network speed can burst at 5000 kbps, then > limit speed is 3000 kbps, or network can burst at 6000 kbps, then limit > speed is 4000 kbps , How fast the network can go is completely random , > especially if multiple virtual machines exist at one ovs bridge . That > sounds weird ! Why we do this at this way, Is there anything I am > misunderstand ? > I was not able to follow your logic completely. Are you suggesting openflow spec to be changed and remove multiple bands? _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
