netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Tomt <andre@tomt.net>
To: Robert Olsson <Robert.Olsson@data.slu.se>
Cc: netdev@oss.sgi.com
Subject: Re: FIB alternative fib_hash2.c
Date: Fri, 15 Apr 2005 19:31:00 +0200	[thread overview]
Message-ID: <425FFA54.9070106@tomt.net> (raw)
In-Reply-To: <16991.54602.218744.163816@robur.slu.se>

Robert Olsson wrote:
> Hello!
> 
> Don't like to sit on this... originally an experiment to understand what we
> can expect from FIB lookup in the linux context. Beginning to think it 
> might be useful as is... memory is cheap. With full bgp and rDoS I see around
> double FIB lookup performance.  No-one has been brave enough to test it....
> Patch is for 2.6.11 and includes an Kconfig option different FIB alternatives.

Drool. Got some numbers? pps - flows - memory use, on what hardware, 
that sort of thing.

  reply	other threads:[~2005-04-15 17:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 14:52 FIB alternative fib_hash2.c Robert Olsson
2005-04-15 17:31 ` Andre Tomt [this message]
2005-04-16  7:23   ` Robert Olsson
2005-04-16  8:55     ` Andre Tomt
2005-04-18 16:06       ` 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=425FFA54.9070106@tomt.net \
    --to=andre@tomt.net \
    --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).