| To: | ralph+d@xxxxxxxxx |
|---|---|
| Subject: | Re: [RFC] High Performance Packet Classifiction for tc framework |
| From: | Jamie Lokier <jamie@xxxxxxxxxxxxx> |
| Date: | Thu, 14 Aug 2003 00:21:58 +0100 |
| Cc: | "netdev@xxxxxxxxxxx" <netdev@xxxxxxxxxxx> |
| In-reply-to: | <Pine.LNX.4.51.0308131707280.21992@xxxxxxxxxxxx> |
| References: | <3F2E5CD6.4030500@xxxxxxxxx> <1060012260.1103.380.camel@xxxxxxxxxxxxxxxx> <3F302E04.1090503@xxxxxxxxx> <1060286331.1025.73.camel@xxxxxxxxxxxxxxxx> <3F381B3E.6080807@xxxxxxxxx> <20030811224050.59bc36fe.davem@xxxxxxxxxx> <20030812142913.GB18802@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.51.0308131320470.13253@xxxxxxxxxxxx> <20030813191757.GE4405@xxxxxxxxxxxxxxxxxx> <Pine.LNX.4.51.0308131707280.21992@xxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
Ralph Doncaster wrote: > So you have to put an entry in the /16 table for every /16 that you have a > more specific route for, right? > Then what if I have 3 different routes; one for 217.109.0.0/16, another > for 217.109.118.0/24 and one for 217.109.118.68/32? Then you would have one entry in the /16 table, matching 217.109.0.0/16, whose BEST value is the first route and whose LARGER points to another table. The second table would have one entry matching 217.109.118.0/24, whose BEST value is the second route, and whose LARGER points to another table. The third table would have one entry matching 217.109.118.68/32, whose BEST value is the third route, and which has no LARGER. That's three hash tables, each containing just one entry. -- Jamie |
| Previous by Date: | [PATCH] (7/11) netrom - convert route/node tables to hlist, Stephen Hemminger |
|---|---|
| Next by Date: | [PATCH] ibmtr - get rid of MOD_INC/DEC, Stephen Hemminger |
| Previous by Thread: | Re: [RFC] High Performance Packet Classifiction for tc framework, Ralph Doncaster |
| Next by Thread: | Fw: [Bugme-new] [Bug 1036] New: Badness in local_bh_enable at kernel/softirq.c:113, Andrew Morton |
| Indexes: | [Date] [Thread] [Top] [All Lists] |