From: Andi Kleen <ak@muc.de>
To: jamal <hadi@cyberus.ca>
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: 5 May 2005 20:07:43 +0200
Date: Thu, 5 May 2005 20:07:43 +0200 [thread overview]
Message-ID: <20050505180743.GC24386@muc.de> (raw)
In-Reply-To: <1115297370.7680.58.camel@localhost.localdomain>
> 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
What I wanted to say is that 99.999% of all users dont need the
cisco grade BGP4 capable standard FIB, it is a just wasted complexity
and memory for them.
> 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?
Yes, and complexity.
-Andi
next prev parent reply other threads:[~2005-05-05 18:07 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 [this message]
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=20050505180743.GC24386@muc.de \
--to=ak@muc.de \
--cc=Jens.Laas@data.slu.se \
--cc=Robert.Olsson@data.slu.se \
--cc=hadi@cyberus.ca \
--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).