I don't think the driver can use DMA. If you need more speed than 26
MBits/s, you might have to go through the USB interface. We hit a
similar issue of wanting to get full 100 mbit speed of the ethernet
and realizing that the interface to the card is just bit-banging and
won't support much speed. I
Kumar,
There is a limit on the performance of the embedded system imposed by
the speed of your kernel and your hardware, so to first know what are
the max throughput you may get from your platform, you should try to
perform a loopback throughput test. I usually use the iperf tool for
this
Diego Dompe ha scritto:
Bottom line is that I have never seen board with the processing power of
the DM355 provide more than 30MB/s.
Actually, with a "measly" Luminary Stellaris LM3S6965 (cortex-M3 operating a 50
MHz) I've got a clean data bandwidth of about 21 Mbps with the lwIP HTTP server.
It's not a matter of the processor. It's a matter of the interface
from the processor to the ethernet card. There is no DMA. The
bandwidth is severely limited at the hardware level.
Chris
On Sun, Aug 10, 2008 at 7:18 AM, Lorenzo Lutti <[EMAIL PROTECTED]> wrote:
> Diego Dompe ha scritto:
>
>> Bo
Hi,
We have done performance tests using iperf to measure the throughput from
DM9000 ethernet driver. The 26Mbps reported in the datasheet was done using
TCP. The unpublished number using UDP is about 30Mbps rx and 45 Mbps tx. These
were very optimal numbers since no other application was runn
> Are you saying that 'dm9000 driver doesn't support DMA, that ARM doesn't
> support DMA (seems strange...), or whatelse?
DM9000 uses simple "DMA" to offload driver from pointer increment operation
when copying packets from its FIFO to driver memory space.
DM355 has EDMA provisions for vario
