[osv-dev] Re: Memory layout

2019-09-05 Thread pusnow . kaist
Great, Thanks! 2019년 9월 5일 목요일 오후 12시 58분 56초 UTC+9, Waldek Kozaczuk 님의 말: > > There is no official Wiki but details of this issue should give you an > idea - https://github.com/cloudius-systems/osv/issues/1043 also this > commit that has changed kernel placement - >

Re: [osv-dev] Demand paging for malloc

2019-09-10 Thread pusnow . kaist
I mean "allocated but not used" case. In the example, it only uses the first 4KB of 512MB. 4KB is a small portion of 128MB. I also totally agree with mmap-backed malloc for large memory allocation. Wonsup Yoon 2019년 9월 10일 화요일 오후 3시 52분 52초 UTC+9, Nadav Har'El 님의 말: > > > On Mon, Sep 9,

[osv-dev] Re: Demand paging for malloc

2019-09-09 Thread pusnow . kaist
It only fails on firecracker whose default memory size is 128M. For QEMU, if I set VM's memory to 128M, it also fails. ./scripts/build -j24 image=native-example && ./scripts/run.py -m 128M trace: OSv v0.53.0-87-gf7b6bee5 eth0: 192.168.122.15 Booted up in 345.76 ms Hello from main allocation