From: jamal <hadi@cyberus.ca>
To: Andi Kleen <ak@muc.de>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
Jens.Laas@data.slu.se, netdev@oss.sgi.com
Subject: Re: (diet-)FIB alternative fib_hlist.c
Date: Thu, 05 May 2005 08:49:29 -0400 [thread overview]
Message-ID: <1115297370.7680.58.camel@localhost.localdomain> (raw)
In-Reply-To: <m1zmvax2cx.fsf@muc.de>
On Wed, 2005-04-05 at 20:39 +0200, Andi Kleen wrote:
> Robert Olsson <Robert.Olsson@data.slu.se> writes:
>
> > Hello!
> >
> > fib_hlist is the smallest and simpliest routing algo we could think of
> > it's just a sorted (h)list.
> >
> > routing (FIB lookup) performance. dst hash is not used.
> >
> > fib_hlist fib_hash test routing table size
> > -----------------------------------------------------
> > 444 kpps 433 kpps Single flow. local=19/main=5 entries
> > 433 kpps 431 kpps rDoS. local=19/main=5
> > 0.2 kpps 198 kpps rDoS local=19/main=123946
> >
> Great patch! I wanted to do something like this for a long time :/
> It is a good solution for 99.999% of all users who never have more
> than a few routes.
>
Great patch it is - but why do you say "99.999% of all users" feel they
would love this? Clearly perfomance at the low routes area is not
something that is a huge difference against standard fib. And you suffer
miserably at latge route size.
Is it memory consumption you are thinking of?
cheers,
jamal
next prev parent reply other threads:[~2005-05-05 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-04 16:10 (diet-)FIB alternative fib_hlist.c Robert Olsson
2005-05-04 18:39 ` Andi Kleen
2005-05-04 20:10 ` Robert Olsson
2005-05-05 12:49 ` jamal [this message]
2005-05-05 18:07 ` Andi Kleen
2005-05-05 19:54 ` Andre Tomt
2005-05-06 11:31 ` Robert Olsson
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=1115297370.7680.58.camel@localhost.localdomain \
--to=hadi@cyberus.ca \
--cc=Jens.Laas@data.slu.se \
--cc=Robert.Olsson@data.slu.se \
--cc=ak@muc.de \
--cc=netdev@oss.sgi.com \
/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).