| To: | "Mathieu Giguere" <Mathieu.Giguere@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries. |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Thu, 8 Apr 2004 11:33:50 -0700 |
| Cc: | ak@xxxxxx, netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx |
| In-reply-to: | <012201c41d94$cee1b400$0348858e@D4SF2B21> |
| References: | <1IJuR-8qH-39@xxxxxxxxxxxxxxxx> <m3ptaiwfpq.fsf@xxxxxxxxxxxxxxxxxxxxxx> <012201c41d94$cee1b400$0348858e@D4SF2B21> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Thu, 8 Apr 2004 14:10:43 -0400 "Mathieu Giguere" <Mathieu.Giguere@xxxxxxxxxxx> wrote: > The main goal to remove the routing cache is to avoid to have 4096 routes > limitation This 4K routes limitation is news to everyone who works on this code. When nexthop changes we _MUST_ flush PMTU etc. information because that could have changed. If however, such information is locked into the route itself, it will propagate immediately into the routing cache entry once recreated. You seem to be talking about a lot of non-problems, but this may because you're not providing enough details. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries., alex |
|---|---|
| Next by Date: | RE: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries., Mathieu Giguere |
| Previous by Thread: | Re: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries., alex |
| Next by Thread: | RE: IPv4 and IPv6 stack multi-FIB, scalable in the million of entries., Mathieu Giguere |
| Indexes: | [Date] [Thread] [Top] [All Lists] |