Re: [ovs-dev] [PATCH] dpif-netdev: Remove meter rate from the bucket size calculation.

2021-05-19 Thread Ilya Maximets
On 4/21/21 3:48 PM, Ilya Maximets wrote: > Implementation of meters supposed to be a classic token bucket with 2 > typical parameters: rate and burst size. > > Burst size in this schema is the maximum number of bytes/packets that > could pass without being rate limited. > > Recent changes to

Re: [ovs-dev] [PATCH] dpif-netdev: Remove meter rate from the bucket size calculation.

2021-05-12 Thread Tonghao Zhang
On Wed, Apr 21, 2021 at 9:48 PM Ilya Maximets wrote: > > Implementation of meters supposed to be a classic token bucket with 2 > typical parameters: rate and burst size. > > Burst size in this schema is the maximum number of bytes/packets that > could pass without being rate limited. > > Recent

Re: [ovs-dev] [PATCH] dpif-netdev: Remove meter rate from the bucket size calculation.

2021-04-30 Thread Eelco Chaudron
On 21 Apr 2021, at 15:48, Ilya Maximets wrote: > Implementation of meters supposed to be a classic token bucket with 2 > typical parameters: rate and burst size. > > Burst size in this schema is the maximum number of bytes/packets that > could pass without being rate limited. > > Recent

[ovs-dev] [PATCH] dpif-netdev: Remove meter rate from the bucket size calculation.

2021-04-21 Thread Ilya Maximets
Implementation of meters supposed to be a classic token bucket with 2 typical parameters: rate and burst size. Burst size in this schema is the maximum number of bytes/packets that could pass without being rate limited. Recent changes to userspace datapath made meter implementation to be in line