On Mon, 2008-21-07 at 08:11 +0800, Herbert Xu wrote:True. But note: this is only during rule creation - once you create the rule (user space to kernel path), then no more hash table reference. Fast path has already a filter with actions attached, and is a mere pointer dereference. If user<->kernel performance insertion/deletion is important, it is worth it. For example: Dave implemented dynamic hash tables on xfrm (voip setup time with ipsec is a metric used in the industry in that case) . The only operational problem i had with xfrm was lack of an upper bound of how large a table can grow; i would rather user space be told ENOMEM than continuing to grow in some cases (I actually implemented a patch which put a stop after a certain number of sad/spd - but i dont expect hugs if i was to post it;->). cheers, jamal -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Scott Preece | Re: Linux Foundation Technical Advisory Board Elections |
| Luis R. Rodriguez | Re: [Announce] Linux-tiny project revival |
| Andrew Morton | 2.6.23-rc1-mm2 |
| Dave Hansen | [PATCH 02/24] rearrange may_open() to be r/o friendly |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [BUG] New Kernel Bugs |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
