RE: Power PC 440GX Jumbo Packets EMAC2/3
From: zDL Linux PPC <hidden>
Date: 2005-02-24 13:12:21
On Thursday 24 February 2005 12:46, zDL Linux PPC wrote:quoted
I have been doing some experiments with Jumbo packets (MTU9000) and havequoted
noticed that once you exceed the 2KB fifo size, I end upwith no responsequoted
from the box. I can ping the box with no problem at all at sizes greaterthan 2KB, howeverquoted
upon further investigation I noticed packets of size 2006bytes causes noquoted
further packet to be transmitted (adding debug prints toibm_emac_core.c,quoted
the driver believes the packet has been transmitted), afteradding a furtherquoted
42 bytes of header information this comes to the exact sizeof the Transmitquoted
Fifo 2048 (2KB). I have also changed the Transmit FifoRegister to 1024quoted
bytes, this solves the problem at 2006 bytes however now ithas moved to 982quoted
bytes of data (+42bytes of header = 1024) Has anyone else experienced this problem while either usinga smallerquoted
transmit fifo (512 or 1024 bytes) and MTU 1500 or a largerMTU (>2033) andquoted
EMAC transmit fifo of 2048. I guess this will really applyto people withquoted
larger MTU not many will decrease the Tx fifo, and I amfurther guessingquoted
that not many are using 9000 MTU as not much hardware seemsto support it, Iquoted
can only use it through a direct connection between PC'sand not through aquoted
switch! Any suggestions on how to overcome this problem??? My onlyidea is to eitherquoted
add data to the packet (don't think this will work) orforceably fragmentquoted
the packet (if it is 2K in size) to ensure that it neveruses the exact sizequoted
of the tx fifo.....Have you applied Matt Porters patch? It has been submitted at the beginning of this month?
No I haven't seen it on either of these lists, do you know where I can find it Thanks