netdev
[Top] [All Lists]

Re: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries.

To: "Mathieu Giguere" <Mathieu.Giguere@xxxxxxxxxxx>
Subject: Re: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries.
From: Andi Kleen <ak@xxxxxx>
Date: Thu, 08 Apr 2004 19:18:41 +0200
Cc: netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <1IJuR-8qH-39@gated-at.bofh.it> (Mathieu Giguere's message of "Thu, 08 Apr 2004 17:21:01 +0200")
References: <1IJuR-8qH-39@gated-at.bofh.it>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.2 (gnu/linux)
"Mathieu Giguere" <Mathieu.Giguere@xxxxxxxxxxx> writes:

[you should probably discuss that on netdev@xxxxxxxxxxx instead, cc'ed]

>     We currently looking for a multi-FIB, scalable routing table in the
> million of entries, no routing cache for IPv4 and IPv6.  We want a IP stack

No routing cache? Doesn't sound like a good idea.

> that can have a log(n) (or better) insertion/deletion and lookup
> performance.  Predictable performance, even in the million of entries.

And even more vast overkill for most linux users than the existing
routing code already is.  Linux has at least the beginnings of a pluggable
FIB interface (fib_table), which has slightly bit rotted, but probably
not too bad. I would suggest you clean that up, make the existing
hash table really optional and then you can just plug in anything you want.

>     I join a patch with the fib_hash in IPv4 replace with a patricia tree
> ready for multi-FIB base on a 2.4.22 kernel.  This is the beginning of a
> long cleanup.

What do you consider dirty in the current stack? 

-Andi


<Prev in Thread] Current Thread [Next in Thread>