Thx applied to master and backported patch 1 and 3 to branch-2.3.
On Fri, Sep 19, 2014 at 12:42 PM, Flavio Leitner wrote:
> On Thu, Sep 18, 2014 at 03:18:11PM -0700, Alex Wang wrote:
> > When ovs is running with large topology (e.g. large number of
> > interfaces), the stats update to ovsdb beco
On Thu, Sep 18, 2014 at 03:18:11PM -0700, Alex Wang wrote:
> When ovs is running with large topology (e.g. large number of
> interfaces), the stats update to ovsdb becomes huge and normally
> requires multiple run of ovsdb jsonrpc message processing loop to
> consume.
>
> To prevent the periodic s
It is a rate limit. That was a misunderstanding on my part. Go ahead
and call it one.
On Fri, Sep 19, 2014 at 10:40:46AM -0700, Alex Wang wrote:
> Do you think it is better to not call it a 'rate-limit' logic?
>
> On Fri, Sep 19, 2014 at 10:33 AM, Ben Pfaff wrote:
>
> > On Thu, Sep 18, 2014 a
Do you think it is better to not call it a 'rate-limit' logic?
On Fri, Sep 19, 2014 at 10:33 AM, Ben Pfaff wrote:
> On Thu, Sep 18, 2014 at 03:18:11PM -0700, Alex Wang wrote:
> > When ovs is running with large topology (e.g. large number of
> > interfaces), the stats update to ovsdb becomes huge
On Thu, Sep 18, 2014 at 03:18:11PM -0700, Alex Wang wrote:
> When ovs is running with large topology (e.g. large number of
> interfaces), the stats update to ovsdb becomes huge and normally
> requires multiple run of ovsdb jsonrpc message processing loop to
> consume.
>
> To prevent the periodic s
When ovs is running with large topology (e.g. large number of
interfaces), the stats update to ovsdb becomes huge and normally
requires multiple run of ovsdb jsonrpc message processing loop to
consume.
To prevent the periodic stats update from backlogging in the
jsonrpc sending queue, this commit
