[ovs-dev] [branch-1.11] ofproto-dpif: Configure datapath max-idle through ovs-vsctl.

Ben Pfaff blp at nicira.com
Mon Jun 23 17:33:58 UTC 2014


OK. I understand now. Do you still need any reviews?

On Mon, Jun 23, 2014 at 10:30 AM, Alex Wang <alexw at nicira.com> wrote:
> Hey Ben,
>
> Thanks for pointing it out,  I actually do not have a clear judge on this.
> I think it is necessary in this case,
>
> For branch-2.0, we are before the revalidator-as-a-thread era.  So, it is
> pretty
> different from the implementation in commit 72310b04.
>
> For branch-1.11, 1.10, we need to configure the option on a different table.
>
> Thanks,
> Alex Wang,
>
>
>
>
> On Mon, Jun 23, 2014 at 10:23 AM, Ben Pfaff <blp at nicira.com> wrote:
>>
>> On Thu, Jun 19, 2014 at 09:20:57PM -0700, Alex Wang wrote:
>> > This patch adds a new configuration option, "max-idle" to the
>> > Bridge "other-config" column. This sets how long datapath flows,
>> > for the configured bridge, are cached in the datapath before
>> > ovs-vswitchd thread expires them.
>> >
>> > This commit is a backport of commit 72310b04 (upcall: Configure
>> > datapath max-idle through ovs-vsctl.).
>> >
>> > Signed-off-by: Alex Wang <alexw at nicira.com>
>>
>> Were there significant changes in the backports?  It's unusual to post
>> all the versions of a patch to backport, because backports are usually
>> straightforward, so that getting a review on each of them consumes
>> time for both the poster and the reviewer without much reduction of
>> risk.
>
>



-- 
"I don't normally do acked-by's.  I think it's my way of avoiding
getting blamed when it all blows up."               Andrew Morton



More information about the dev mailing list