netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kristen Carlson <kristenc@cs.pdx.edu>
To: netdev@oss.sgi.com
Subject: patricia tries vs. hash for routing?
Date: Thu, 18 Sep 2003 10:29:10 -0700	[thread overview]
Message-ID: <20030918172910.GA22091@sirius.cs.pdx.edu> (raw)

Hi,
I'm wondering if somebody has already written a patch that replaces the
current routing algorithm (hash) with one that is based on a trie based
algorithm?  I'm also wondering if anybody has done any performance 
comparisons with very large route tables to see which one scales better?
thanks,
Kristen
 
-- 
WWXD (What Would Xena Do?) 

             reply	other threads:[~2003-09-18 17:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 17:29 Kristen Carlson [this message]
2003-09-19  3:17 ` patricia tries vs. hash for routing? David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-09-19 21:48 Kristen Carlson
2003-09-20  6:37 ` David S. Miller
2003-10-28 13:29   ` bill davidsen

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=20030918172910.GA22091@sirius.cs.pdx.edu \
    --to=kristenc@cs.pdx.edu \
    --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).