| To: | greearb@xxxxxxxxxxxxxxx (Ben Greear) |
|---|---|
| Subject: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission |
| From: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
| Date: | Sun, 7 Jan 2001 18:30:59 +0000 (GMT) |
| Cc: | alan@xxxxxxxxxxxxxxxxxxx (Alan Cox), davem@xxxxxxxxxx (David S. Miller), linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3A58C3E8.FF5FF68E@xxxxxxxxxxxxxxx> from "Ben Greear" at Jan 07, 2001 12:30:48 PM |
| Sender: | owner-netdev@xxxxxxxxxxx |
> Thats what it already does, if I understand correctly. Of course, if VLAN > is loaded as a module, then it will be in the hash before IP, right? Thats fine. I think it'll be a different hash bucket anyway. The point of having vlan first is that if its not registered or the interface isnt doing vlan there is basically a zero overhead |
| Previous by Date: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Ben Greear |
|---|---|
| Next by Date: | Re: routable interfaces WAS( Re: [PATCH] hashed device lookup (DoesNOT meet Linus' sumission policy!), jamal |
| Previous by Thread: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Ben Greear |
| Next by Thread: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Matti Aarnio |
| Indexes: | [Date] [Thread] [Top] [All Lists] |