From: Andre Tomt <andre@tomt.net>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: netdev@oss.sgi.com, Jens.Laas@data.slu.se
Subject: Re: (diet-)FIB alternative fib_hlist.c
Date: Thu, 05 May 2005 21:54:49 +0200 [thread overview]
Message-ID: <427A7A09.4060900@tomt.net> (raw)
In-Reply-To: <17016.62444.34282.625407@robur.slu.se>
Robert Olsson wrote:
> 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
>
> As seen fib_hlist is catastrophe for large routing tables as expected but
> performs surprisingly well for ordinary routing tables so it should be
> fine for most hosts and servers. The patch has config option to select FIB.
>
> Probably we soon want to specify differnt lookup schemes for different
> tables say for local table fib_hash or fib_hlist. While for large main table
> fib_hash2/fib_trie would be better option.
From a distribution[1] point of view, a boot time option would be much
better than choosing at compile time. Boot time plus a kconfig multiple
selection list would be even better. Another perhaps even more user
friendly option would be setting it runtime using f.ex. iproute, but I
guess that could end up messy..
1. goes for both "a GNU/Linux distribution" and kernel image
distribution in a production network
next prev parent reply other threads:[~2005-05-05 19:54 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
2005-05-05 18:07 ` Andi Kleen
2005-05-05 19:54 ` Andre Tomt [this message]
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=427A7A09.4060900@tomt.net \
--to=andre@tomt.net \
--cc=Jens.Laas@data.slu.se \
--cc=Robert.Olsson@data.slu.se \
--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).