From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ed W Subject: Re: Performance issue due to constant "modprobes" Date: Wed, 20 Apr 2011 09:54:57 +0100 Message-ID: <4DAE9F61.2010103@wildgooses.com> References: <4D9E45C2.7030805@wildgooses.com> <4D9F98D3.5070802@wildgooses.com> <4DA0C402.1090809@wildgooses.com> <4DA58A73.9030308@wildgooses.com> <4DA59881.1050501@wildgooses.com> <4DA5D346.5030303@wildgooses.com> <4DAC67F3.3070503@wildgooses.com> <4DADB406.104060 6@wildgooses.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 7bit Cc: =?ISO-8859-2?Q?Maciej_=AFenczykowski?= , netfilter-devel@vger.kernel.org To: Jozsef Kadlecsik Return-path: Received: from mail1.nippynetworks.com ([91.220.24.129]:41706 "EHLO mail1.nippynetworks.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751867Ab1DTIy7 (ORCPT ); Wed, 20 Apr 2011 04:54:59 -0400 In-Reply-To: Sender: netfilter-devel-owner@vger.kernel.org List-ID: On 20/04/2011 08:31, Jozsef Kadlecsik wrote: > The module "ip_set" is loaded in if the "ipset" program is installed and > invoked on that system. Aha, that is almost certainly the cause. As well as kernel, I had updated the software image to include ipset/conntrack and didn't connect the events I see that I obviously haven't built my image correctly and included the ip_set module - apologies to the iptables folks - obviously user error here.. So, in conclusion, with the two patches from Maciej, there is now no modprobe activity in the event of static iptables and kernel with all modules built-in. Perfect Thanks for everyone's interest in this - superb response Ed W