I had assumed Joe was going to revise this, since I don't think he's pushed it
yet.
--Justin
On Mar 4, 2014, at 9:46 AM, Ben Pfaff wrote:
> Justin, are you planning to apply this then? Or, Joe, are you planning
> to post a new version? Just trying to figure out what's happening.
>
> On Thu
Sorry, I hadn't got around to it yet. I'll repost.
On 4 March 2014 09:46, Ben Pfaff wrote:
> Justin, are you planning to apply this then? Or, Joe, are you planning
> to post a new version? Just trying to figure out what's happening.
>
> On Thu, Feb 27, 2014 at 10:59:00AM -0800, Justin Pettit
Justin, are you planning to apply this then? Or, Joe, are you planning
to post a new version? Just trying to figure out what's happening.
On Thu, Feb 27, 2014 at 10:59:00AM -0800, Justin Pettit wrote:
> I think it's clear enough, since it explicitly mentions datapath
> flows. There's a FAQ entr
I think it's clear enough, since it explicitly mentions datapath flows.
There's a FAQ entry that describes the different types of flows that Ben can
point to, which always makes him happy.
--Justin
On Feb 27, 2014, at 10:55 AM, Joe Stringer wrote:
> I agree, it would be helpful to have a se
I agree, it would be helpful to have a sentence like that.
This could be particularly misleading given that it is relating to datapath
flows, which is completely different from OpenFlow rule timeouts. Do you
think that this is clear enough with the current description?
On 27 February 2014 10:50,
On Feb 27, 2014, at 10:37 AM, Joe Stringer wrote:
> +The maximum idle time in milliseconds for flows to be cached in
> the
> +datapath. A lower value may improve flow setup performance, but
> +decrease the number of cached flows in the datapath. Conversely,
>
This patch adds a new configuration option, "max-idle" to the
Open_vSwitch "other-config" column. This sets how long datapath flows
are cached in the datapath before revalidators expire them.
Signed-off-by: Joe Stringer
---
v5: Rebase.
v4: Remove extra "max_idle" from Flow_Table table.
v3: Use '
