| To: | Wang Jian <lark@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] improvement on net/sched/cls_fw.c's hash function |
| From: | Thomas Graf <tgraf@xxxxxxx> |
| Date: | Tue, 5 Apr 2005 12:38:27 +0200 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <20050405140342.024A.LARK@linux.net.cn> |
| References: | <20050405133336.0247.LARK@linux.net.cn> <20050404223744.1f04c130.davem@davemloft.net> <20050405140342.024A.LARK@linux.net.cn> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
* Wang Jian <20050405140342.024A.LARK@xxxxxxxxxxxx> 2005-04-05 14:05 > New patch attached. Hashsize is 256, the same as old one. Do you have any numbers that could prove that this change actually improves the hash distribution and thus the overall lookup performance? The most often used and thus most important range of mark values is definitely 0..255. I did not look into jhash but the risk of collisions definitely increases with this change which affects about 90% of the users of fw which could benefit from a collision free hashtable so far. I would appreciate if you could provide some numbers proving both the need and actual improvement of this change since fwmark is one of the most often used classifiers. Cheers |
| Previous by Date: | Re: take 2-2 WAS(Re: PATCH: IPSEC xfrm events, jamal |
|---|---|
| Next by Date: | Re: [IPSEC]: Kill nested read lock by deleting xfrm_init_tempsel, Herbert Xu |
| Previous by Thread: | Re: [PATCH] improvement on net/sched/cls_fw.c's hash function, jamal |
| Next by Thread: | Re: [PATCH] improvement on net/sched/cls_fw.c's hash function, Wang Jian |
| Indexes: | [Date] [Thread] [Top] [All Lists] |