mmap support?

[piranna]

Does runtime.js support mmap? I know we don't have support for devices, but having so, we could have all the storage space mmap'ed and use it as main memory. This way, we could have an instant-on system working the ram just as a (big) disk cache, and also we could deprecate the concept of files hierarchy and just use raw objects as storage, as it was commented in other threads. Performance would not degrade but in fact it could be increased by not needing to copy the data twice (disk -> disk cache -> process memory). It could be a problem when working with "pure" variables that are not supposed to be stored, but they could be flagged some way to don't be backed (first candidates I can think are let and const defined ones). What do you think?

[RossComputerGuy]

I can add this into my multiarchitecture port of Runtime, I include i386/x86 as an architecture.

[piranna]

This is not an easy task, probably the first thing that would be needed to have is virtual memory, so later there would be some mapping from the virtual addresses to the file itself...

[RossComputerGuy]

I'm able to do that

[austinfrey]

I'm interested in this also, more specifically I'm interested to know if data can be saved to disk without a file system. for instance can an array, buffer, or object be saved directly to disk without a file system and then accessed just by it's location on disk instead. is this currently possible?

[piranna]

then accessed just by it's location on disk instead

That's just what filesystems does under the hood... :-D

[austinfrey]

@piranna to your point though, are you looking to get rid of the FS construct though? and use more JS constructs(objects)?

[piranna]

@piranna to your point though, are you looking to get rid of the FS construct though? and use more JS constructs(objects)?

Yes, sort of.