| To: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: CONFIG_IPV6_SUBTREES (was [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6) |
| From: | Ville Nuorvala <vnuorval@xxxxxxxxxx> |
| Date: | Fri, 6 Jun 2003 14:16:57 +0300 (EEST) |
| Cc: | davem@xxxxxxxxxx, <kuznet@xxxxxxxxxxxxx>, <netdev@xxxxxxxxxxx>, <ajtuomin@xxxxxxxxxxxxxxxxxxx>, <lpetande@xxxxxxxxxxxxxxxxxxx>, <jagana@xxxxxxxxxx>, <kumarkr@xxxxxxxxxx>, <nakam@xxxxxxxxxxxxxx>, <usagi-core@xxxxxxxxxxxxxx> |
| In-reply-to: | <20030606.193218.117654914.yoshfuji@linux-ipv6.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 6 Jun 2003, YOSHIFUJI Hideaki / [iso-2022-jp] 吉藤英明 wrote: > Excuse me, please forget anything related to "Mobile IP" during this > discussion; do not assume that Mobile IP is the only user of > CONFIG_IPV6_SUBTREES. At the moment it is :) I was just making a point about the IMHO flawed semantics of CONFIG_IPV6_SUBTREES. If you keep the original (first dest, then src) key ordering you basically can't use the subtrees for anything else but storing source address specific host routes. With the reversed order you can do a lot more... -Ville -- Ville Nuorvala Research Assistant, Institute of Digital Communications, Helsinki University of Technology email: vnuorval@xxxxxxxxxx, phone: +358 (0)9 451 5257 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6, Henrik Petander |
|---|---|
| Next by Date: | Re: [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6, Masahide NAKAMURA |
| Previous by Thread: | Re: CONFIG_IPV6_SUBTREES (was [patch]: CONFIG_IPV6_SUBTREES fix for MIPv6), YOSHIFUJI Hideaki / 吉藤英明 |
| Next by Thread: | [PATCH] move dmascc away from setup.c, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |