netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <jdb@comx.dk>
To: Netfilter Developers <netfilter-devel@vger.kernel.org>,
	Patrick McHardy <kaber@trash.net>
Cc: Harald Welte <laforge@netfilter.org>,
	Martin Josefsson <gandalf@netfilter.org>,
	Jesper Dangaard Brouer <jdb@comx.dk>
Subject: [PATCH 0/3] Solve scalability issue for chain list "name" searching
Date: Fri, 21 Dec 2007 14:44:19 +0100	[thread overview]
Message-ID: <1198244659.23885.8.camel@localhost.localdomain> (raw)


Primary focus, of this patch set, is to solve a scalability issue; For
chain list "name" searching. Functions:
iptcc_find_label(),iptc_is_chain().

It also includes a patch for inline'ing some functions, and
introducing a chain counter.

The main patch still include some debugging print statements, that can
be enabled by defining "DEBUG" when compiling the code.  This kept to
allow an easier code review.

The patches and test scripts, can also be found here:
 http://people.netfilter.org/hawk/patches/scalability/bsearch/

The patches are tested against SVN r7147.

-- 
Med venlig hilsen / Best regards
  Jesper Brouer
  ComX Networks A/S
  Linux Network developer
  Cand. Scient Datalog / MSc.
  Author of http://adsl-optimizer.dk
  LinkedIn: http://www.linkedin.com/in/brouer

             reply	other threads:[~2007-12-21 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 13:44 Jesper Dangaard Brouer [this message]
2007-12-21 13:46 ` [PATCH 1/3] Inline functions iptcc_is_builtin() and set_changed() Jesper Dangaard Brouer
2008-01-15 17:01   ` Patrick McHardy
2007-12-21 13:47 ` [PATCH 2/3] Introduce a counter for number of user defined chains Jesper Dangaard Brouer
2008-01-15 17:06   ` Patrick McHardy
2007-12-21 13:50 ` [PATCH 3/3] Solving scalability issue: for chain list "name" searching Jesper Dangaard Brouer
2008-01-15 17:18   ` 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=1198244659.23885.8.camel@localhost.localdomain \
    --to=jdb@comx.dk \
    --cc=gandalf@netfilter.org \
    --cc=kaber@trash.net \
    --cc=laforge@netfilter.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).