From: "David S. Miller" <davem@redhat.com>
To: Michael Bellion and Thomas Heinz <nf@hipac.org>
Cc: hadi@cyberus.ca, linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: [RFC] High Performance Packet Classifiction for tc framework
Date: Mon, 11 Aug 2003 22:40:50 -0700 [thread overview]
Message-ID: <20030811224050.59bc36fe.davem@redhat.com> (raw)
In-Reply-To: <3F381B3E.6080807@hipac.org>
On Tue, 12 Aug 2003 00:39:58 +0200
Michael Bellion and Thomas Heinz <nf@hipac.org> wrote:
> This is a fundamental issue related to the use of hashes in this
> context. It shows that it is _impossible_ to create a hash which
> meets the requirement of O(1) rules per bucket in the setting
> described above regardless how clever you choose the hash function.
>
> What do you think about it? Do you agree?
The ipv4 FIB hash tables tackle exactly this problem. The resulting
worse cast complexity is O(n_bits_in_prefix_mask).
The problem you've described is exactly the same as trying to use
hashing for routing tables.
next prev parent reply other threads:[~2003-08-12 5:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-14 8:45 [RFC] High Performance Packet Classifiction for tc framework Michael Bellion and Thomas Heinz
2003-07-16 5:02 ` jamal
2003-07-17 13:13 ` Michael Bellion and Thomas Heinz
2003-08-03 18:14 ` jamal
2003-08-04 13:17 ` Michael Bellion and Thomas Heinz
2003-08-04 15:51 ` jamal
2003-08-05 22:21 ` Michael Bellion and Thomas Heinz
2003-08-07 19:58 ` jamal
2003-08-07 20:05 ` David S. Miller
2003-08-08 21:51 ` jamal
2003-08-09 0:01 ` David S. Miller
2003-08-11 22:39 ` Michael Bellion and Thomas Heinz
2003-08-12 2:57 ` jamal
2003-08-12 14:56 ` Michael Bellion and Thomas Heinz
2003-08-12 15:41 ` jamal
2003-08-12 5:40 ` David S. Miller [this message]
2003-08-12 14:29 ` Jamie Lokier
2003-08-12 15:39 ` Michael Bellion and Thomas Heinz
2003-08-15 14:28 ` Jamie Lokier
2003-08-13 17:28 ` Ralph Doncaster
2003-08-13 19:17 ` Jamie Lokier
2003-08-13 21:10 ` Ralph Doncaster
2003-08-13 23:21 ` Jamie Lokier
2003-08-12 14:56 ` Michael Bellion and Thomas Heinz
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=20030811224050.59bc36fe.davem@redhat.com \
--to=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=nf@hipac.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).