Search found 18 matches

by zhu48
Tue Aug 23, 2016 4:03 am
Forum: General Discussion and Feedback
Topic: Blog: Google SoC lwIP Report Week 13
Replies: 5
Views: 6280

Re: Blog: Google SoC lwIP Report Week 13

I will not be able to continue working on this into the coming school year. Full web browser support will definitely have to be done by somebody else, and I cannot honestly say how difficult that will be.
by zhu48
Fri Aug 19, 2016 6:00 pm
Forum: General Discussion and Feedback
Topic: Blog: Google SoC lwIP Report Week 10
Replies: 34
Views: 27995

Re: Blog: Google SoC lwIP Report Week 10

Regarding mTCP being a user library... But how much is the first one relevant to ReactOS? The problem with a user-mode library is that there's no quick and easy way to turn it into a good driver. You can re-wrap it into a standard API like WinSock, or you can port the algorithms into kernel code. Wr...
by zhu48
Wed Aug 17, 2016 6:57 pm
Forum: General Discussion and Feedback
Topic: Blog: Google SoC lwIP Report Week 10
Replies: 34
Views: 27995

Re: Blog: Google SoC lwIP Report Week 10

mTCP looks like a highly involved and highly optimized TCP implementation targeted towards POSIX systems. To integrate it transparently into ReactOS as the primary TCP driver seems to me like a larger task than doing our own implementation of their optimization techniques. Many of mTCP's optimizatio...
by zhu48
Wed Aug 17, 2016 4:08 pm
Forum: General Discussion and Feedback
Topic: Blog: Google SoC lwIP Report Week 10
Replies: 34
Views: 27995

Re: Blog: Google SoC lwIP Report Week 10

Interesting. I will take a look at this thing, see how it compares.
Something to note, lwIP 2.0.0 was recently released with better multithreading support in its netconn API. It is, however, still a big global lock approacand not designed from the ground up to be thread safe.
by zhu48
Sat Aug 06, 2016 6:29 pm
Forum: General Discussion and Feedback
Topic: Blog: Google SoC lwIP Report Week 10
Replies: 34
Views: 27995

Re: Blog: Google SoC lwIP Report Week 10

I've been going through a lot of deadlock fixes for the last two days. I introduced new ones in the latest commit that's on SVN, but the one before that one actually works quite well. The latest commit was an attempt to fix cancellation issues. I've been working since then, and this issue you're see...