From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Shaun R." <mailinglists@unix-scripts.com>
Subject: CONFIG_IP_NF_CONNTRACK
Date: Tue, 17 Jul 2007 02:14:56 -0700
Message-ID: <f7i1ai$cs4$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

I've read in a few other posts on this ML that this option cripples linux 
performance when compiled into the kernel.  I'm wondering though, in the 
messages i read it talked about it crippling performance when built into 
dom0, what about the domU's.  I've been seeing problems with Guests network 
locking up with eth0 error stating full queue.  On dom0 i have 
CONFIG_IP_NF_CONNTRACK set as a module and it's not loaded, but on DomU's 
it's included into the kernel.


~Shaun