From: "Neal P. Murphy" <neal.p.murphy@alum.wpi.edu>
To: Jan Engelhardt <jengelh@inai.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: xtables-addons 64-bit counter patch
Date: Sun, 7 Jun 2015 01:21:59 -0400 [thread overview]
Message-ID: <20150607012159.492666d6@playground> (raw)
In-Reply-To: <alpine.LSU.2.20.1506061315120.29092@nerf40.vanv.qr>
On Sat, 6 Jun 2015 13:15:38 +0200 (CEST)
Jan Engelhardt <jengelh@inai.de> wrote:
> x
> On Friday 2015-06-05 00:04, Neal P. Murphy wrote:
> >The theory:
> > - Use two kernel pages for the counters for each group of 256
> > addresses.
> > - Change counters to 64-bit.
> > - Change to __get_free_pages/free_pages, using order=2 (two
> > consecutive pages), and zero both pages.
> > - Change "%u" to "%llu" as needed.
> > - Everything else pretty much stays the same.
> >
> >I also changed tmpbuf to two pages (Justin Case's idea), but I
> >don't know if that's really necessary.
> >
> >Did I miss anything?
>
> I applied it.
Thanks! It never occurred to me that a long long might someday be
longer than 64 bits. And I haven't had to program C structs for more
than one ARCH for around 25 years, when I had to make a home-brew
DB work on m68k, m88k, Sparc and MIPS. Using about as many different
compilers and OSes. *I* thought I was being clever using explicit
padding to align elements by hand. I've applied your tweaks to my patch.
Neal
next prev parent reply other threads:[~2015-06-07 5:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 22:04 xtables-addons 64-bit counter patch Neal P. Murphy
2015-06-06 11:15 ` Jan Engelhardt
2015-06-07 5:21 ` Neal P. Murphy [this message]
2015-10-19 5:34 ` Neal P. Murphy
2015-11-08 23:49 ` Neal P. Murphy
2015-11-09 9:14 ` Jan Engelhardt
2015-11-09 21:34 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150607012159.492666d6@playground \
--to=neal.p.murphy@alum.wpi.edu \
--cc=jengelh@inai.de \
--cc=netfilter-devel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.