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

Re: [Xen-devel] [patch merge tree] netfront needs more headroom

To: Gerd Knorr <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] [patch merge tree] netfront needs more headroom
From: Christian Limpach <christian.limpach@xxxxxxxxx>
Date: Thu, 8 Dec 2005 10:50:17 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>
Delivery-date: Thu, 08 Dec 2005 18:51:03 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UZZ3zZX4l6XQXonSNKsHYTn8T9f2Nw3zbzNGeHHRMj4kmTnCPR/O3Bi1j5HU12i5sSlusMJVZmu5JjejlLj9lMcePaR0RBf6KHn/zyhI3HeKK1K4zp4zm8YT47HrSwpn68fn+nI0ZirgosRWv3bj1Ab05+z4wrtOuVh9rNmFZKs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <43970452.9080508@xxxxxxx>
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>
References: <43970452.9080508@xxxxxxx>
Reply-to: Christian.Limpach@xxxxxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 12/7/05, Gerd Knorr <kraxel@xxxxxxx> wrote:
> Raised the headrum size from 200 to 512.  I've got "Received packet
> needs 120 bytes more headroom." in my syslog, so 200 is obviously too small.
>
> Increased to 512 as the slab allocator gives out pieces of memory with
> sizes being powers of two, so the old allocation size already was 256
> and anything larger than that will end up being 512 anyway (unless we
> create our own memory pool with custom size ...)

We believe that this is fixed by recent changes to the network driver,
notably these changesets in xen-unstable:
linux-2.6-xen-sparse cset: 4e9c643968ffd0526258dc1ae7d1fee6123be718
linux-2.6-xen-sparse cset: c976c1ff806aa46c989fb5b1d84b311519fb0456

     christian

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

<Prev in Thread] Current Thread [Next in Thread>