Thread (10 messages) 10 messages, 4 authors, 2007-09-12

Re: [PATCH] Fix e100 on systems that have cache incoherent DMA

From: Kok, Auke <hidden>
Date: 2007-09-07 21:18:54

Kok, Auke wrote:
David Acker wrote:
quoted
Kok, Auke wrote:
quoted
first impressions are not good: pings are erratic and shoot up to 3 
seconds. In an overnight stress test, the receive unit went offline and 
never came back up (TX still working).

it sounds like something in the logic is suspending the ru too much, but 
I haven't had time to look deeply into the code yet.
I don't have an e100 enabled x86 box handy but I will look into getting one setup.

I just applied this patch to my PXA255 based system http://www.compulab.co.il/x255/html/x255-cm-datasheet.htm .
It is running 2.6.18.4 plus compulab patches plus some hostap patches plus the e100 patch.  I get:

pings going from the embedded system to a desktop machine.
100 packets transmitted, 100 received, 0% packet loss, time 98996ms
rtt min/avg/max/mdev = 0.239/0.728/1.512/0.571 ms

Pings going the from the desktop machine to the embedded system
100 packets transmitted, 100 received, 0% packet loss, time 99217ms
rtt min/avg/max/mdev = 0.206/0.876/1.473/0.575 ms
ok, I just got a note from our lab saying that that particular system has the 
freak ping times even without your patch applied 8)

ignoring the ping issue, we still have the ru offline, but that could have 
possibly been caused by whatever is causing this ping issue... More testing is 
needed, and I'll try to find a system without the ping issue here first.
update: Emil reports that the unit with the RU hang did not have bad ping times 
to begin with, pointing to a problem with the patch for sure now...

Auke
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help