WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] CONFIG_IP_NF_CONNTRACK

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] CONFIG_IP_NF_CONNTRACK
From: "Shaun R." <mailinglists@xxxxxxxxxxxxxxxx>
Date: Tue, 17 Jul 2007 02:14:56 -0700
Delivery-date: Tue, 17 Jul 2007 02:13:10 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] CONFIG_IP_NF_CONNTRACK, Shaun R. <=