From: "Philip R. Auld" <pauld@egenera.com>
Subject: [PATCH] Increase MAX_SKBUFF_ORDER
Date: Thu, 10 Nov 2005 15:43:31 -0500
Message-ID: <20051110204331.GR7401@vienna.egenera.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
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


Hi,
	The recent (changeset 7700) switch to use the architecture
specific skbuff allocation routine breaks with very large MTU sizes.
The below patch raises the MAX_SKBUFF_ORDER to 3. Could this be 
applied to make it the default?

Thanks,

Phil


Signed-Off-by: Philip Auld <pauld@egenera.com>

diff -r 136b2d20dc81 linux-2.6-xen-sparse/arch/xen/kernel/skbuff.c
--- a/linux-2.6-xen-sparse/arch/xen/kernel/skbuff.c	Wed Nov  9 15:08:37 2005
+++ b/linux-2.6-xen-sparse/arch/xen/kernel/skbuff.c	Thu Nov 10 09:40:26 2005
@@ -17,7 +17,7 @@
 /* Referenced in netback.c. */
 /*static*/ kmem_cache_t *skbuff_cachep;
 
-#define MAX_SKBUFF_ORDER 2
+#define MAX_SKBUFF_ORDER 3
 static kmem_cache_t *skbuff_order_cachep[MAX_SKBUFF_ORDER + 1];
 
 static struct {





-- 
Philip R. Auld, Ph.D.  	        	       Egenera, Inc.    
Software Architect                            165 Forest St.
(508) 858-2628                            Marlboro, MA 01752