Hello,
## Background
I'm currently writing a research paper about
"A Comparison of different TCP Implementations"
comparing LWIP TCP with Linux TCP.
Besides
* a statical code analysis
* and a semantic analysis
(reading, understanding and explaining/comparing
the code)
I plan to inclu
Keep in mind the 'lw' in 'lwIP' stands for 'lightweight'.
I guess you are thinking in terms of the socket API, but lwIP can run
without an OS; it is more suited to a small embedded system than a
computer. In this context, you use the RAW API, which is event driven.
I guess you can benefit from
Richard Siegfried wrote:
> For linux this is easy, because I have some experience using ftrace.
Then why don't you use the linux port from contrib?
Simon
___
lwip-users mailing list
lwip-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-
On 12/12/16 14:58, Simon Goldschmidt wrote:
> Richard Siegfried wrote:
>> For linux this is easy, because I have some experience using ftrace.
>
> Then why don't you use the linux port from contrib?
Especially building as a shared lib might be quite usefull.
Thank you!
signature.asc
Descriptio
On 12/12/16 14:20, Sergio R. Caprile wrote:
> Keep in mind the 'lw' in 'lwIP' stands for 'lightweight'.
> I guess you are thinking in terms of the socket API, but lwIP can run
> without an OS; it is more suited to a small embedded system than a
> computer. In this context, you use the RAW API, whic
