netfront needs more headroom
PATCH 1/1 netfront needs more headroom
Hi,
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 ...)
cheers,
Gerd
Subject: xen netfront driver needs more headroom
From: [email protected]
drivers/xen/netfront/netfront.c +1 -1
@@ -77,7 +77,7 @@ }while (0 ) /* Allow headroom on each rx pkt for Ethernet header, alignment padding, ... */ -#define RX_HEADROOM 200 +#define RX_HEADROOM 512static unsigned long rx_pfn_array[NET_RX_RING_SIZE ];static multicall_entry_t rx_mcl[NET_RX_RING_SIZE +1 ];
_______________________________________________
Xen-devel mailing list
[email protected]
http://lists.xensource.com/xen-devel
Quoted 7 lines · Gerd Knorr
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
Quoted 7 lines
Quoted 2 lines
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.
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:4e9c643968ffd0526258dc1ae7d1fee6123be718linux-2.6-xen-sparse cset:c976c1ff806aa46c989fb5b1d84b311519fb0456
Yep, patch looks ok and the problem seems to be gone.
cheers,
Gerd