On Thu, Sep 18, 2014 at 2:48 PM, Ben Pfaff wrote:
> On Thu, Sep 18, 2014 at 05:24:12PM -0300, Flavio Leitner wrote:
>> On Thu, Sep 18, 2014 at 01:18:57PM -0700, Ethan Jackson wrote:
>> > In our experience, most people actually expect this number to be
>> > fairly high. For example, our traffic ge
On Thu, Sep 18, 2014 at 05:24:12PM -0300, Flavio Leitner wrote:
> On Thu, Sep 18, 2014 at 01:18:57PM -0700, Ethan Jackson wrote:
> > In our experience, most people actually expect this number to be
> > fairly high. For example, our traffic generator runs a little bit of
> > traffic to populate cac
On Thu, Sep 18, 2014 at 01:18:57PM -0700, Ethan Jackson wrote:
> In our experience, most people actually expect this number to be
> fairly high. For example, our traffic generator runs a little bit of
> traffic to populate caches, pauses for a couple of seconds, before
> finally starting the main
In our experience, most people actually expect this number to be
fairly high. For example, our traffic generator runs a little bit of
traffic to populate caches, pauses for a couple of seconds, before
finally starting the main test. On top of that, we've had some minor
complaints from people mana
On Fri, Sep 12, 2014 at 10:03:56AM +1200, Joe Stringer wrote:
> The datapath max_idle value determines how long to wait before deleting
> an idle datapath flow when operating below the flow_limit. This patch
> increases the max_idle to 10 seconds, which allows datapath flows to be
> remain cached e
Thanks, applied to master.
On 15 September 2014 09:41, Ethan Jackson wrote:
> Acked-by: Ethan Jackson
>
>
> On Thu, Sep 11, 2014 at 3:03 PM, Joe Stringer
> wrote:
> > The datapath max_idle value determines how long to wait before deleting
> > an idle datapath flow when operating below the flow
Acked-by: Ethan Jackson
On Thu, Sep 11, 2014 at 3:03 PM, Joe Stringer wrote:
> The datapath max_idle value determines how long to wait before deleting
> an idle datapath flow when operating below the flow_limit. This patch
> increases the max_idle to 10 seconds, which allows datapath flows to b
The datapath max_idle value determines how long to wait before deleting
an idle datapath flow when operating below the flow_limit. This patch
increases the max_idle to 10 seconds, which allows datapath flows to be
remain cached even if they are used less consistently, and provides a
small improveme
