| 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 13:50:08 +0000 (GMT) |
| Cc: | ak@xxxxxxx (Andi Kleen), linux-kernel@xxxxxxxxxxxxxxx (linux-kernel), netdev@xxxxxxxxxxx (netdev@xxxxxxxxxxx) |
| In-reply-to: | <3A580B31.7998C783@candelatech.com> from "Ben Greear" at Jan 06, 2001 11:22:41 PM |
| Sender: | owner-netdev@xxxxxxxxxxx |
> Suppose I bind a raw socket to device vlan4001 (ie I have 4k in the list > before that one!!). Currently, that means a linear search on all devices, > right? In that extreme example, I would expect the hash to be very > useful. At this point you have to ask 'why is vlan4001 an interface'. Would it not be cleaner to add the vlan id to the entries in the list of addresses per interface ? |
| Previous by Date: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Alan Cox |
|---|---|
| Next by Date: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Matti Aarnio |
| Previous by Thread: | Re: [PATCH] hashed device lookup (New Benchmarks), Andi Kleen |
| Next by Thread: | Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission, Ben Greear |
| Indexes: | [Date] [Thread] [Top] [All Lists] |