From: Stanislav Kruchinin <stas@crypt.org.ru>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Massive filtering
Date: Tue, 08 May 2007 18:10:40 +0000 [thread overview]
Message-ID: <4640BD20.5030306@crypt.org.ru> (raw)
In-Reply-To: <200705050130.AA2025718096@ipro.net>
ericr wrote:
> My first thought for scaling up was to use the hash tables, and I am
> feeling that the last line in lartc's document page "12.4. Hashing filters
> for very fast massive filtering" which says "Note that this example could
> be improved to the ideal case where each chain contains 1 filter!" is a
> little misleading since no divisor above 256 works. On first reading, I 'm
> thinking, yeh, I'll just put a divisor of 16777216 and my problems are
> solved... nope.. wrong answer. I haven't even gotten to the point where I
> issue 32 million filter rules to tc and see if it chokes.
The only solution in the case of thousands of rules is the u32 classifier with
hashing filters. Unfortunately, divisor's upper limit is 256, and it's not
appropriate for the practical tasks. From the other side, hashes with very
large number of buckets (like 16777216, you said) can't be implemented,
because they will require much more RAM than you can address.
I have similar task and some days ago started to work on patches for tc and
u32 classifier that will allow to use large hashes (see my recent messages at
linux-net@ mailing list archive). I'm a newbie in a Linux kernel and I can't
complete this task fast. I think we should ask for help from experienced
developers.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2007-05-08 18:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-05 5:30 [LARTC] Massive filtering ericr
2007-05-05 6:15 ` Vladimir Vitkov
2007-05-08 18:10 ` Stanislav Kruchinin [this message]
2007-05-12 21:51 ` Corey Hickey
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=4640BD20.5030306@crypt.org.ru \
--to=stas@crypt.org.ru \
--cc=lartc@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.