On Thu, May 2, 2013 at 9:35 PM, Levi Pearson <[email protected]> wrote:
> Actually, mmap() is often the best way to deal with gigantic files, so > long as you have sufficient address space (not physical memory, but > bus width!) to deal with them. I vaguely recall something to do with private address space for MAP_PRIVATE and how Linux handled the memory for that. It must not be the case now though. I just fallocate'd a 100GB file and mmap()'ed it without issue. Has something changed recently (10 years since I've used C/mmap)? /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
