| To: | pekkas@xxxxxxxxxx |
|---|---|
| Subject: | Re: [PATCH] Prefix List patch against 2.5.70 |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Mon, 02 Jun 2003 21:49:41 -0700 (PDT) |
| Cc: | dlstevens@xxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx, krkumar@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, linux-net@xxxxxxxxxxxxxxx |
| In-reply-to: | <Pine.LNX.4.44.0306030746420.8936-100000@xxxxxxxxxx> |
| References: | <OF0DFD7FB1.3567B088-ON88256D39.00724E19@xxxxxxxxxx> <Pine.LNX.4.44.0306030746420.8936-100000@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Pekka Savola <pekkas@xxxxxxxxxx> Date: Tue, 3 Jun 2003 07:48:13 +0300 (EEST) Umm.. every prefix should have an interface route, so they're a required subset of the routing table, correct? That's entirely correct, thanks for noticing this :-) This is why I said that they could add to a global list all routes that meet this criteria. Thus making any querying mechanism simple to implement. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Prefix List patch against 2.5.70, Pekka Savola |
|---|---|
| Next by Date: | Re: [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6, Ville Nuorvala |
| Previous by Thread: | Re: [PATCH] Prefix List patch against 2.5.70, Pekka Savola |
| Next by Thread: | Re: [PATCH] Prefix List patch against 2.5.70, David Stevens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |