I tend to think about mmap the same way I do about vfork: with the right virtual memory system and file system it shouldn't be necessary. A combination of demand paging and copy-on-write should make read/write of large areas of files as efficient as memory mapping - the main difference being that, with read/write, memory is isolated from both the file and other processes, whereas memory mapping implies some degree of sharing. On the whole I think I'd rather have the isolation.
Failable I/O will clearly mix badly with demand paging, but I think the solution is to make the I/O not fail. ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te8d7c6e48b5c075b-M4339bf8c643a58a78486b7e8 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
