> Sorry, this was wrong. I mean this (as you suggested):
>
> +OVS_VSCTL_CHECK_RX_PKT([p1], [1])
> dnl advance the clock by 100K ms, the previous 'recv' should be updated.
> -for i in `seq 0 100`; do ovs-appctl time/warp 1000; done
> +for i in `seq 0 99`; do ovs-appctl time/warp 1000; done
> OVS
Thx for the review, applied to master, branch-2.2
On Thu, May 1, 2014 at 7:21 PM, Joe Stringer wrote:
> On 30 April 2014 12:46, Alex Wang wrote:
>>
>> +dnl set the stats update interval to 100K ms, the following 'recv'
>> should not be updated.
>> +AT_CHECK([ovs-vsctl set O . other_config:stat
On Fri, May 2, 2014 at 1:14 PM, Alex Wang wrote:
>
>
>
> On Thu, May 1, 2014 at 7:21 PM, Joe Stringer wrote:
>
>> On 30 April 2014 12:46, Alex Wang wrote:
>>>
>>> +dnl set the stats update interval to 100K ms, the following 'recv'
>>> should not be updated.
>>> +AT_CHECK([ovs-vsctl set O . other
On Thu, May 1, 2014 at 7:21 PM, Joe Stringer wrote:
> On 30 April 2014 12:46, Alex Wang wrote:
>>
>> +dnl set the stats update interval to 100K ms, the following 'recv'
>> should not be updated.
>> +AT_CHECK([ovs-vsctl set O . other_config:stats-update-interval=10])
>> +for i in `seq 0 50`;
On 30 April 2014 12:46, Alex Wang wrote:
>
> +dnl set the stats update interval to 100K ms, the following 'recv' should
> not be updated.
> +AT_CHECK([ovs-vsctl set O . other_config:stats-update-interval=10])
> +for i in `seq 0 50`; do ovs-appctl time/warp 1000; done
> +for i in `seq 1 5`; do
This commit adds a new configuration "stats-update-interval" in
"other_config" of Open_Vswitch table. So users can control the
statistics update frequency. A possible use case is that, users
can lower the update frequency to reduce the cpu consumption of
the ovs-vswitchd thread.
The configured v
