4 ms·
It seems like a strange match to use LwIP (which is optimzed for small size to run on embedded systems) with a kernel optimized for speed. I'm guessing that a d
by m_eiman 12y ago
It seems like a strange match to use LwIP (which is optimzed for small size to run on embedded systems) with a kernel optimized for speed. I'm guessing that a different IP stack would perform better, given the different constraints on a x64 system. Maybe there aren't many to choose from though, that aren't tied to a specific kernel?
- errordeveloper 12y agoI agree. Something like mTCP [1] would make more sense, if this is for cloud-based systems... [1]: https://github.com/eunyoung14/mtcp https://github.com/eunyoung14/mtcp
- justincormack 12y agoYou can use the NetBSD stack[1] on baremetal/in userspace/wherever. [1] http://rumpkernel.org/ http://rumpkernel.org/
- errordeveloper 12y agoYeah, exactly. NetBSD's implementation makes sense to use, as it's a rather solid one and very portable. Plus it's probably very general-purpose, while lwIP had never been. Not to say that general-purposeness is the best thing, so that's why I pointed at mTCP, which is actually optimised for multicore systems... Anyhow, I don't think these guys even get their point across. Why have they chosen lwIP in this particular instance actually?
- justincormack 12y agoYes, lwIP only has smallness as a benefit, at the expense of a lot. If we knew what the idea behind the thing was it might be clearer, performance does seem to be an aim.