From: Robert Olsson <Robert.Olsson@data.slu.se>
To: Andre Tomt <andre@tomt.net>
Cc: Robert Olsson <Robert.Olsson@data.slu.se>,
netdev@oss.sgi.com, Jens.Laas@data.slu.se
Subject: Re: (diet-)FIB alternative fib_hlist.c
Date: Fri, 6 May 2005 13:31:14 +0200 [thread overview]
Message-ID: <17019.21890.234387.549229@robur.slu.se> (raw)
In-Reply-To: <427A7A09.4060900@tomt.net>
Andre Tomt writes:
> > 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..
Yes I'll guess kernel config would be the first step. Also we need to
find out if there are any useful options to current FIB. Which is very
general purpose.
Anyway we have a cleaner interface to FIB also we have some new FIB options.
Which should be a step forward and an advantage for linux and will hopefully
lead to more development and understanding and so that Linux will used for
development in this area. We will also lead to better understand the dst
hash and FIB trade off.
Experiences from tests or use are very welcome.
Cheers.
--ro
prev parent reply other threads:[~2005-05-06 11:31 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
2005-05-06 11:31 ` Robert Olsson [this message]
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=17019.21890.234387.549229@robur.slu.se \
--to=robert.olsson@data.slu.se \
--cc=Jens.Laas@data.slu.se \
--cc=andre@tomt.net \
--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).