[MLton-devel] Re: pinned large arrays

[Henry Cejtin]

One  problem  with  locking  down memory locations for lots of big objects is
that in the modern world it isn't only memory that is `scarce',  it  is  also
address  space.  Unless Stephen puts in hacks to let the from and to space be
non-contiguous, pinning a bunch of small objects can  really  hurt  you.   In
general  you  only  have  about  2  gig  of  usable address space for mmaping
(because of the space required for the stack and the break and space required
for shared libraries), so this can really hurt.

Again,  I'm  not  arguing  against  the notion of using mmap, just that these
kinds of things are probably better done in C routines accessible from  MLton
programs.

_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that's a super model! Visit http://clustering.foundries.sf.net/

_______________________________________________
MLton-devel mailing list
MLton-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mlton-devel