On Mon Apr 4 11:19:37 EDT 2011, rminn...@gmail.com wrote: > On Sun, Apr 3, 2011 at 2:24 PM, erik quanstrom <quans...@labs.coraid.com> > wrote: > >> The reason it doesn't work on 9vx is because the 32 bit Go runtime > >> reserves a large chunk of address space (currently 768mb). On all > >> other platforms, this is accomplised with an mmap equivalient, which > >> we all know won't work on Plan 9. > >> > > > > if i read the thread on this topic correctly, this reservation > > isn't necessary on plan 9, since there are no shared libraries > > and the heap will always be contiguous. > > > > no, the shared libraries are not going to affect the heap size. > Certainly not to this scale. >
i'm not quite sure what you're saying "no" to. in any event, my understanding is, it's not the size of the heap, it's the heap's continuity. if the heap is not contiguous, you'll need a structure tracking it. according to lwn http://lwn.net/Articles/428100/ In the process of trying to reach that goal of "low enough overhead and no significant latency," the Go developers have made some simplifying assumptions, one of which is that the memory being managed for a running application comes from a single, virtually-contiguous address range. this is the whole point of the big allocation, so why would we drag this into plan 9, when it's not necessary. the plan 9 heap is contiguous. - erik
