All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denys Fedoryschenko <denys@visp.net.lb>
To: Patrick McHardy <kaber@trash.net>
Cc: Meelis Roos <mroos@linux.ee>, netdev@vger.kernel.org
Subject: Re: [ANNOUNCE]: First release of nftables
Date: Wed, 18 Mar 2009 16:52:27 +0200	[thread overview]
Message-ID: <200903181652.27928.denys@visp.net.lb> (raw)
In-Reply-To: <49C107AB.1030003@trash.net>

On Wednesday 18 March 2009 16:39:39 Patrick McHardy wrote:
>
> On top it has far smaller code and less memory usage as soon as
> you have more than one CPU, its lockless, no default counters,
> no overhead for unused chains, etc etc.
>
> When the time has come, I will of course post benchmarks.
>
Thanks a lot for your code Patrick.
I will try as soon as i can.

I dont think hash and rbtrees is suboptimal.
I have really a lot of situations where i need large set of ip's or ports to 
be added in similar rule, which is forced to be linear. And if i even build 
tree manually - it will be really headache to add new hosts.

nftables looks very promissing in this case

  reply	other threads:[~2009-03-18 14:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090318112937.675BF13A4B0@koiott.tartu-labor>
2009-03-18 12:00 ` [ANNOUNCE]: First release of nftables Meelis Roos
2009-03-18 14:39   ` Patrick McHardy
2009-03-18 14:52     ` Denys Fedoryschenko [this message]
2009-03-18 14:58       ` Patrick McHardy
2009-03-18  4:29 Patrick McHardy
2009-03-18  8:13 ` Jan Engelhardt
2009-03-18  8:21   ` Patrick McHardy
2009-03-18  8:28 ` Patrick McHardy
     [not found]   ` <20090318092039.GA2511@squirrel.roonstrasse.net>
2009-03-18  9:52     ` Patrick McHardy
2009-03-18  9:58 ` Andi Kleen
2009-03-18 10:04   ` Patrick McHardy
2009-03-18 10:13     ` Varun Chandramohan
2009-03-18 10:17       ` Patrick McHardy

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=200903181652.27928.denys@visp.net.lb \
    --to=denys@visp.net.lb \
    --cc=kaber@trash.net \
    --cc=mroos@linux.ee \
    --cc=netdev@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.