From: Richard Siegfried <richard_siegfried@systemli.org>
To: lwip-devel <lwip-devel@nongnu.org>, netdev@vger.kernel.org
Subject: Paper: A Comparison of TCP Implementations, Linux vs. lwIP
Date: Thu, 18 May 2017 21:13:09 +0200 [thread overview]
Message-ID: <b9da121b-b881-42d8-94f2-0e1f9ef46428@systemli.org> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 528 bytes --]
Hello,
Some months ago I wrote a paper on a Comparison of TCP Implementations.
(Features, Code Quality, Data Structures, etc.)
https://github.com/richi235/A-Comparison-of-TCP-Implementations
It's finished and the corresponding exam successfully passed.
But I thought perhaps this could be interesting for some people here, too.
And since im still interested in and reading about TCP Implementations
I'm thankfull for any feedback, corrections or opinions about the
conclusions I found.
Thanks,
-- Richard
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 529 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
lwip-devel mailing list
lwip-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/lwip-devel
reply other threads:[~2017-05-18 19:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9da121b-b881-42d8-94f2-0e1f9ef46428@systemli.org \
--to=richard_siegfried@systemli.org \
--cc=lwip-devel@nongnu.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox