[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <577FDCC1.4000509@akamai.com>
Date: Fri, 8 Jul 2016 13:02:57 -0400
From: Vishwanath Pai <vpai@...mai.com>
To: David Laight <David.Laight@...LAB.COM>,
"pablo@...filter.org" <pablo@...filter.org>,
"kaber@...sh.net" <kaber@...sh.net>,
"kadlec@...ckhole.kfki.hu" <kadlec@...ckhole.kfki.hu>
Cc: "johunt@...mai.com" <johunt@...mai.com>,
"netfilter-devel@...r.kernel.org" <netfilter-devel@...r.kernel.org>,
"coreteam@...filter.org" <coreteam@...filter.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"pai.vishwain@...il.com" <pai.vishwain@...il.com>
Subject: Re: [PATCH v2 1/2] libxt_hashlimit: Prepare libxt_hashlimit.c for
revision 2
On 07/08/2016 12:54 PM, Vishwanath Pai wrote:
> On 07/08/2016 12:37 PM, David Laight wrote:
>> If you think some users would still want 32bit limits, then you should
>> (probably) use a _64 suffix for the new functions.
>>
>> David
>
> I am proposing a new revision for hashlimit that supports a higher rate
> along with a few other changes/fixes (in separate patches). Hence the
> prefix _v2 for the new functions.
>
> - Vish
>
I'm sorry _v1 for the old functions, the new functions (for rev2) don't
have a suffix.
Powered by blists - more mailing lists