Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] ipv4: Remove fib_hash.
Date: Wed, 02 Feb 2011 01:48:13 +0100	[thread overview]
Message-ID: <1296607693.2607.7.camel@edumazet-laptop> (raw)
In-Reply-To: <20110201.151941.48509941.davem@davemloft.net>

Le mardi 01 février 2011 à 15:19 -0800, David Miller a écrit :
> The time has finally come to remove the hash based routing table
> implementation in ipv4.
> 
> FIB Trie is mature, well tested, and I've done an audit of it's code
> to confirm that it implements insert, delete, and lookup with the same
> identical semantics as fib_hash did.
> 
> If there are any semantic differences found in fib_trie, we should
> simply fix them.
> 
> I've placed the trie statistic config option under advanced router
> configuration.
> 
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---

Hmm... I know having to maintain two implementations is time consuming,
but I know fib_trie is bigger :

# size net/ipv4/fib_*.o
   text	   data	    bss	    dec	    hex	filename
   7252	    120	      0	   7372	   1ccc	net/ipv4/fib_frontend.o
   7279	     16	      4	   7299	   1c83	net/ipv4/fib_hash.o
   1479	      0	      0	   1479	    5c7	net/ipv4/fib_rules.o
   7885	      0	   2080	   9965	   26ed	net/ipv4/fib_semantics.o
  16222	     16	     16	  16254	   3f7e	net/ipv4/fib_trie.o

In my tests, I know that fib_trie is more expensive for typical routing
tables for hosts (no more than a dozen or entries), in latencies
results, mostly because of icache misses, but also dcache ones.

Thanks



  parent reply	other threads:[~2011-02-02  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-01 23:19 [PATCH] ipv4: Remove fib_hash David Miller
2011-02-01 23:26 ` Stephen Hemminger
2011-02-01 23:33   ` Stephen Hemminger
2011-02-01 23:35     ` David Miller
2011-02-02  0:48 ` Eric Dumazet [this message]
2011-02-02  2:15   ` David Miller
2011-02-02 16:29     ` Stephen Hemminger
2011-02-02 21:51       ` David Miller

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=1296607693.2607.7.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /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