From: Gerd Knorr <kraxel@suse.de>
To: xen-devel <xen-devel@lists.xensource.com>
Cc: Jan Beulich <JBeulich@novell.com>
Subject: [patch merge tree] netfront needs more headroom
Date: Wed, 07 Dec 2005 16:48:34 +0100 [thread overview]
Message-ID: <43970452.9080508@suse.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
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
[-- Attachment #2: xen3-fixup-net-headroom --]
[-- Type: text/plain, Size: 644 bytes --]
Subject: xen netfront driver needs more headroom
From: kraxel@suse.de
Index: linux-2.6.14/drivers/xen/netfront/netfront.c
===================================================================
--- linux-2.6.14.orig/drivers/xen/netfront/netfront.c 2005-12-07 16:26:12.000000000 +0100
+++ linux-2.6.14/drivers/xen/netfront/netfront.c 2005-12-07 16:27:47.000000000 +0100
@@ -77,7 +77,7 @@
} while (0)
/* Allow headroom on each rx pkt for Ethernet header, alignment padding, ... */
-#define RX_HEADROOM 200
+#define RX_HEADROOM 512
static unsigned long rx_pfn_array[NET_RX_RING_SIZE];
static multicall_entry_t rx_mcl[NET_RX_RING_SIZE+1];
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-12-07 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 15:48 Gerd Knorr [this message]
2005-12-08 18:50 ` [patch merge tree] netfront needs more headroom Christian Limpach
2005-12-09 11:23 ` Gerd Knorr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43970452.9080508@suse.de \
--to=kraxel@suse.de \
--cc=JBeulich@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.