That's what I get with non-debug version of dm9000.device. A4000 with 68030/25MHz and 2MB of Chip RAM, 0MB of Fast RAM, 64MB of Zorro III RAM clocked at 100MHz.
NETIO - Network Throughput Benchmark, Version 1.32
(C) 1997-2012 Kai Uwe Rommel
UDP server listening.
TCP server listening.
TCP connection established ...
Receiving from client, packet size 1k ... 135.32 KByte/s
Sending to client, packet size 1k ... 7.59 KByte/s
Receiving from client, packet size 2k ... 143.53 KByte/s
Sending to client, packet size 2k ... 149.24 KByte/s
Receiving from client, packet size 4k ... 146.89 KByte/s
Sending to client, packet size 4k ... 151.80 KByte/s
Receiving from client, packet size 8k ... 142.36 KByte/s
Sending to client, packet size 8k ... 156.03 KByte/s
Receiving from client, packet size 16k ... 144.04 KByte/s
Sending to client, packet size 16k ... 155.74 KByte/s
Receiving from client, packet size 32k ... 134.22 KByte/s
Sending to client, packet size 32k ... 157.05 KByte/s
Done.
I wonder if tweaking the priorities of RX/TX routines would give any boost. Also will try moving to INT6 chain, although I don't think this will improve things dramatically. The CNet driver is able to squeeze ~500KBytes through pccard interface, which is also sharing the INT2 interrupt.
I can use WGET to upgrade the device driver by simply pulling the new version from my PC over HTTP. So I'm judging the single TCP connection kinda works more or less stable. (Obviously even less). A mix of WGETs and pings also run in parallel quite all right, with sanautil on top of that. However, when the FTP opens second socket in passive mode it never gets the remote directory listing. I can see the listing in tcpdumped packets, probably the device driver does something odd to them upon reception.
Oh, and MiamiDX cannot complete DHCP configuration for some reason, as opposed to Roadshow. Perhaps I will need more packet dumping inside the device driver.