![]() | ||||||||||
Messages in this thread |
David Miller wrote: > From: Jesper Krogh <jesper@krogh.cc> > Date: Sat, 10 May 2008 13:01:08 +0200 > >> Any good suggestions about the "Transmit timed out" messages. It >> currently leads to a system that "doesnt die" but doesnt respond within >> 15 minutes of load of the network adapter. > > It's likely some bug in the driver that hangs the card for whatever > reason, which we'll need to work out. Ok. I have been testing a bit more. It generally works fine, It seems the "transmit timed out" thing was provoked by dd in the tests, because it was creating a lot of small requests. (default bs=512).(over NFS). When the blocksize went up, the problem dissapered. (and the numer of context-switches went down). When the blocksize went up, the performance likewise raised to 615MB/s. I haven't been able to get pass that number. This is where one of the cpu's are settling at 100% load. Jesper -- Jesper -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2008-05-12 08:55 [W:0.187 / U:0.530 seconds] ©2003-2008 Jasper Spaans | ||||||||||