From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vishwanath Pai Subject: Re: [PATCH v2 1/2] libxt_hashlimit: Prepare libxt_hashlimit.c for revision 2 Date: Fri, 8 Jul 2016 12:54:39 -0400 Message-ID: <577FDACF.7020101@akamai.com> References: <20160707233419.GC5026@akamai.com> <063D6719AE5E284EB5DD2968C1650D6D5F4F3704@AcuExch.aculab.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: "johunt@akamai.com" , "netfilter-devel@vger.kernel.org" , "coreteam@netfilter.org" , "netdev@vger.kernel.org" , "pai.vishwain@gmail.com" To: David Laight , "pablo@netfilter.org" , "kaber@trash.net" , "kadlec@blackhole.kfki.hu" Return-path: In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D5F4F3704@AcuExch.aculab.com> Sender: netdev-owner@vger.kernel.org List-Id: netfilter-devel.vger.kernel.org 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