Charles, I hate to jump in so late in the game but I was wondering about 2 things that relate to this patches:
1. Do you happen to have any automated tests that test OSv networking stack beyond what the unit tests do? Have you by any chance created any documentation about OSv networking implementation? I myself have very little understanding of it and it took me a while for example to fix this issue - https://github.com/cloudius-systems/osv/issues/859#issuecomment-384636059. 2. I am thinking of improvements to OSv that might be part of next 0.53 release (I am planning to cut 0.52 soon). The overall theme, I was going to propose, would be make OSv lighter in terms of memory usage that is also heavily influenced by kernel size (right now around 10MB). Therefore I was wondering what your thoughts are about possibly modularizing networking stack in OSv into tcp, udp, IPV4, IPV6, etc using #ifdef-s (I know that some of these would overlap so what I am proposing may not make much sense especially given how little I know about networking). I am guessing that data structures would be difficult to break like this but code might be easier. Anyway just food for thought. Thanks in advance for your answers, Waldek On Monday, September 10, 2018 at 7:19:11 PM UTC-4, Charles Myers wrote: > > Sorry for delay. A lot of things came up and I finally have some time now > to work on addressing the comments in your review. > > The IPv6 patch set is kind of large and posting it multiple times will be > a bit painful for everyone, so I will provide a link to a github branch > with the changes as you suggested in a day or so. > > Thanks, > Charles > -- You received this message because you are subscribed to the Google Groups "OSv Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
