| To: | hadi@xxxxxxxxxx |
|---|---|
| Subject: | Re: [RFC] High Performance Packet Classifiction for tc framework |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Fri, 8 Aug 2003 17:01:30 -0700 |
| Cc: | nf@xxxxxxxxx, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <1060379500.1723.214.camel@xxxxxxxxxxxxxxxx> |
| References: | <200307141045.40999.nf@xxxxxxxxx> <1058328537.1797.24.camel@xxxxxxxxxxxxxxxx> <3F16A0E5.1080007@xxxxxxxxx> <1059934468.1103.41.camel@xxxxxxxxxxxxxxxx> <3F2E5CD6.4030500@xxxxxxxxx> <1060012260.1103.380.camel@xxxxxxxxxxxxxxxx> <3F302E04.1090503@xxxxxxxxx> <1060286331.1025.73.camel@xxxxxxxxxxxxxxxx> <20030807130502.4af9c815.davem@xxxxxxxxxx> <1060379500.1723.214.camel@xxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On 08 Aug 2003 17:51:40 -0400 jamal <hadi@xxxxxxxxxx> wrote: > Its easy to use hashes when you know that you need to > find example ip src/dst. Jenkins is rather agnostic about the input bits, that's what makes it so powerful. It performs about as well for random input as it does for input which has various patterns. Wait, are you saying the input key size can change? Yes, that's an interesting problem. But for things where you always want some 96-bit key, Jenkins is probably best. |
| Previous by Date: | A question on inet_select_addr(), ahtraps |
|---|---|
| Next by Date: | Re: RFR: new SiS gige driver, David S. Miller |
| Previous by Thread: | Re: [RFC] High Performance Packet Classifiction for tc framework, jamal |
| Next by Thread: | Re: [RFC] High Performance Packet Classifiction for tc framework, Michael Bellion and Thomas Heinz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |