[osv-dev] Re: Page fault when using hitting /os/threads -> regression

2019-08-07 Thread Waldek Kozaczuk
Sent a patch addressing it. It would be nice to run some sort of code quality tool against OSv to find these kinds of nasty bugs. I thought we did run at some point. On Monday, August 5, 2019 at 11:58:21 AM UTC-4, Waldek Kozaczuk wrote: > > This smells like a bug in core/mempool.cc where one of

[osv-dev] [PATCH] scheduler: Initialize _cpu field in detached_state struct

2019-08-07 Thread Waldemar Kozaczuk
The patch 97fe8aa3d2d8f2c938fcaa379c44ae5a80dfbf33 enhanced OSv to start using physical memory below 2MiB. The second MiB is part of the memory where OSv copies compressed kernel to uncompress it later to loader.elf which means it contains garbage (non-0). This one-liner patch explicitly initializ

Re: [osv-dev] Re: Compiler optimization flags to improve OSv performance

2019-08-07 Thread Nadav Har'El
On Wed, Aug 7, 2019 at 8:30 PM Waldek Kozaczuk wrote: > Hi, > > On Tuesday, August 6, 2019 at 12:45:09 PM UTC-4, Joe Duarte wrote: >> >> Hi all, >> >> I think there might be an opportunity for good speedups in OSv if modern >> compiler optimization options are used. >> > Before you start discussi

[osv-dev] Re: Compiler optimization flags to improve OSv performance

2019-08-07 Thread Waldek Kozaczuk
Forgot about this one - https://github.com/cloudius-systems/osv/issues/28 (Optimize atomic operations on UP (single-VCPU). Nadav wrote it originally many years ago, so I do not know how relevant it still is. Anway all the issues I have mentioned in this email I am planning to tackle for next 0

[osv-dev] Re: Compiler optimization flags to improve OSv performance

2019-08-07 Thread Waldek Kozaczuk
Hi, On Tuesday, August 6, 2019 at 12:45:09 PM UTC-4, Joe Duarte wrote: > > Hi all, > > I think there might be an opportunity for good speedups in OSv if modern > compiler optimization options are used. -flto (gcc's Link Time > Optimization, or what Visual Studio calls Whole Program Optimization)

Re: [osv-dev] OSv and IncludeOS

2019-08-07 Thread Waldek Kozaczuk
Firecracker can run on Nitro (i3 bate metal instances) and it is what AWS uses for lambdas and EKS I believe. -- 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 t

Re: [osv-dev] OSv and IncludeOS

2019-08-07 Thread Waldek Kozaczuk
Hi, On Tuesday, August 6, 2019 at 12:43:18 PM UTC-4, Nadav Har'El wrote: > > On Tue, Aug 6, 2019 at 7:21 PM Joe Duarte > wrote: > >> Hi all, >> >> Has anyone tested both OSv and IncludeOS , >> or evaluated them as alternatives? I'd be curious to know the results of >

Re: [osv-dev] OSv and IncludeOS

2019-08-07 Thread Joe Duarte
On Tuesday, August 6, 2019 at 9:43:18 AM UTC-7, Nadav Har'El wrote: > > > I don't know about IncludeOS, but the reason why OSv doesn't run on "bare > metal" is the drivers: When you run on bare metal, you suddenly need to be > able to drive all these dozens of different types of disks, network