On Friday 2011-04-08 19:11, Ed W wrote: >Starting "shorewall" >- using busybox modprobe + released iptables = several minutes... >- module-init-tools + released iptables = 12s >- module-init-tools + your commit = 7.7s >- module-init-tools + patching out modprobe completely = 4.9s > >So, whilst your patch has a huge positive benefit, I'm still seeing a >substantial amount of cpu going to useless modprobing. Which is only natural, because the kernel loads stuff. If you have a problem with time (why so?) you should <*> the xtables modules, and just leave iptables in its origin state. >Of the rest of my 4.9s, 97% of that is waiting for iptables and tc to do >stuff. I need to profile further to see where the delays are though Just how often are you calling iptables, anyway? -- To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
