Re: [lwip-users] LWIP -> Microblaze

[Christiaan Simons]

Lachlan wrote:

> Q:  Can anyone point me to an updated version of xemacif.c that
> would correct these problems. ?

The authorative source is the contrib/ports/v2pro/netif/xemacif.c.
If that file is broken, we want to fix it there. I can have a quick peek,
but I can't guarantee it gets fixed. (I don't have the Xilinx development
environment)

> Q:  Has anyone experienced similar latency problems in the
read(...)function.?

I know the sequential / socket API performs slow
and has some unclear bugs and design flaws.
See also http://savannah.nongnu.org/bugs/?func=detailitem&item_id=15926

What I can tell fore sure this code is slow because
there are too many thread synchronisation waitstates.

When using the lower level raw-API, the achievable
performance levels are much better. Some users have
implemented and alternative socket layer on top of the raw-API.

Christiaan Simons

Hardware Designer
Axon Digital Design

http://www.axon.tv