# Google SoC lwIP Report Week 9

DevFeed: [Google SoC lwIP Report Week 9](<https://devfeed.tech/articles/google-soc-lwip-report-week-9-32795.md>)

Original publisher: [Read original article](<https://reactos.org/blogs/google-soc-lwip-report-week-9/>)

Published: 2016-07-25T00:00:00Z

Content type: article

Language: en

Sources: [Front Page on ReactOS Website](<https://devfeed.tech/sources/front-page-on-reactos-website.md>)

Topics: [lwIP](<https://devfeed.tech/topics/lwip.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [Code review](<https://devfeed.tech/topics/code-review.md>)

Tags: [free](<https://devfeed.tech/tags/free.md>), [kernel](<https://devfeed.tech/tags/kernel.md>), [locking](<https://devfeed.tech/tags/locking.md>), [locks](<https://devfeed.tech/tags/locks.md>), [lwip](<https://devfeed.tech/tags/lwip.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [os](<https://devfeed.tech/tags/os.md>), [react](<https://devfeed.tech/tags/react.md>), [reactos](<https://devfeed.tech/tags/reactos.md>), [thread](<https://devfeed.tech/tags/thread.md>), [win32](<https://devfeed.tech/tags/win32.md>), [winapi](<https://devfeed.tech/tags/winapi.md>)

## AI overview

A week 9 Google Summer of Code report describes an unsuccessful attempt to make lwIP thread-safe. The author examines lwIP's TCP control-block lists and locking system, tests global-lock approaches, and finds that a kernel spin lock severely reduces performance in the ReactOS network-driver context.

## Source excerpt

Last week ended with my realization that lwIP was not thread-safe, and me reading up on various ways to get around that. Last weekend, I spent a lot of time tinkering with lwIP's core code to see how hard it would be to make it thread-safe. I ultimately failed to actually make the library thread-safe, but I did learn a lot of things about lwIP that I hadn't known before I started digging into the source code in so much depth.