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/
Home Products Support Community News


Re: [Xen-devel] help with horrible network failures

To: Rob Gardner <rob.gardner@xxxxxx>
Subject: Re: [Xen-devel] help with horrible network failures
From: Nivedita Singhvi <niv@xxxxxxxxxx>
Date: Wed, 02 Mar 2005 15:43:52 -0800
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 02 Mar 2005 23:46:37 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <422643B9.6030902@xxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E33B5@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <422601A0.3000108@xxxxxx> <422607F4.4040105@xxxxxxxxxx> <422643B9.6030902@xxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Rob Gardner wrote:

My current configuration has:
# CONFIG_E100_NAPI is not set

Isn't that the same as it being disabled? Or should I change it to:

That means NAPI is off, but from what Jon said earlier,
it's ignoring the compile option.

I'm afraid that isn't easy to accomplish. I am working with another researcher in a faraway land, and so I do not have direct control over their machine. Changing their nic could take a while.

That's ok - it wasn't critical.

Sorry, ethtool can't be used to disable/enable NAPI. Ignore
this idiot, neuron misfire...

So,,, what's the conclusion?

Er, that was just saying that ethtool couldn't be used
to alter this - you had to recompile the kernel in order to
disable/enable NAPI in the e100. And it's unclear whether
you are actually disabling it since it is always on. Not
sure what the maintainers intended, there, but claimed to
be fixed very recently..

However, I think you have two problems here - the
ASSERTION is one of them - but not the fatal problem - the
bad address in wakeup_common is the fatal error.
It would help if you could run some debug code (?),
unless someone on the Xen team or on this list has seen
that one before and knows what's going on..

Your sysctl settings would be helpful, too..

None of the following is very relevant to your
oops, but will help in your testing..

Could you turn this on? (this might affect the
assertion - but it's just playing with the race
window, really)..

net.ipv4.tcp_low_latency = 0
echo 1 > net.ipv4.tcp_low_latency

BTW, if you are running httperf, you would probably
benefit from increasing your socket buffer sizes from
the default.
net.ipv4.tcp_rmem = 4096    87380    174760
4096 109568 109568

net.ipv4.tcp_wmem = 4096    16384    131072
4096 109568 109568

net.ipv4.tcp_mem = 12288    16384    24576
122880 163840 245760

net.core.optmem_max = 10240


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
Xen-devel mailing list