[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20171113.103721.6933678238170867.davem@davemloft.net>
Date: Mon, 13 Nov 2017 10:37:21 +0900 (KST)
From: David Miller <davem@...emloft.net>
To: pshelar@....org
Cc: azhou@....org, netdev@...r.kernel.org, joe@....org,
gvrose8192@...il.com
Subject: Re: [net-next v5 0/4] Openvswitch meter action
From: Pravin Shelar <pshelar@....org>
Date: Sat, 11 Nov 2017 07:25:30 +0530
> On Sat, Nov 11, 2017 at 1:39 AM, Andy Zhou <azhou@....org> wrote:
>> This patch series is the first attempt to add openvswitch
>> meter support. We have previously experimented with adding
>> metering support in nftables. However 1) It was not clear
>> how to expose a named nftables object cleanly, and 2)
>> the logic that implements metering is quite small, < 100 lines
>> of code.
>>
>> With those two observations, it seems cleaner to add meter
>> support in the openvswitch module directly.
>>
>> ---
>>
>> v1(RFC)->v2: remove unused code improve locking
>> and other review comments
>> v2 -> v3: rebase
>> v3 -> v4: fix undefined "__udivdi3" references on 32 bit builds.
>> use div_u64() instead.
>> v4 -> v5: rebase
>>
> Acked-by: Pravin B Shelar <pshelar@....org>
Series applied, thanks.
Powered by blists - more mailing lists