> > Connection tracking:
> Fix perfomance problems with this thing. You may have seen reports of
> performance degradation it introduces. I was hoping to take a look at some
> point time hasnt been visiting this side.
One obvious problem that it has is that it uses vmalloc to allocate its
big hash table. This will likely lead to TLB thrashing on a busy box. It should
try to allocate the hashtable with get_free_pages() first and only fall
back to vmalloc if that fails. This way it would run with large pages.
(case in point: we have at least one report that routing
performance breaks down with ip_conntrack when memory size is increased over
1GB on P3s. The hash table size depends on the memory size. The problem does
not occur on P4s. P4s have larger TLBs than P3s.)