o be honest
> the OSv memory footprint has been fine for our application usage
>
> so I haven’t really looked at this.
>
If you have any other ideas of what and possibly improve OSv please let me
know.
>
>
> -Charles
>
>
>
>
>
> *From:* osv...@go
: osv-dev@googlegroups.com On Behalf Of Waldek
Kozaczuk
Sent: Tuesday, October 2, 2018 12:08 PM
To: OSv Development
Subject: Re: [PATCH 00/16] OSv IPv6 support
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
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 networki
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
On Tue, Aug 7, 2018 at 5:49 AM, Charles Myers
wrote:
> This patch series adds IPv6 support to OSv.
>
> The first 5 parts of the series should have no impact on existing
> OSv code. The rest of the patches starting from the net channel
> changes do impact existing code.
>
Thanks. Very impressive
This patch series adds IPv6 support to OSv.
The first 5 parts of the series should have no impact on existing
OSv code. The rest of the patches starting from the net channel
changes do impact existing code.
All parts should compile and test without issues, but IPv6 is only
enabled with the last
On Sat, Aug 4, 2018 at 6:00 AM, Charles Myers
wrote:
> It took me a while to split out the patches according to your guidelines,
> since they were not organized that way.
> I will be submitting them probably starting tomorrow or maybe early next
> week. The largest patch will be around 1 MB for
It took me a while to split out the patches according to your guidelines,
since they were not organized that way.
I will be submitting them probably starting tomorrow or maybe early next
week. The largest patch will be around 1 MB for the unmodified IPv6 .c
files.
Each part of the series should
