Brynet-net wrote:
But RAM isn't non-volatile... I can't find your logic, is it missing?
It would basically be a saved paged (if that makes since).
pcmattman wrote:
Hard drive access is much slower than the RAM, which is why programs take a while to load.
it would only be as slow as when read a page from disk.
frank wrote:
It would waste hard drive space for one thing and programs usually have configuration files and save files for non-volatile storage. I am assuming you mean non-volatile storage like when a computer saves everything in memory to disk like when you hibernate the computer, except that you are planning on only saving the programs memory image.
The program could save it's data structures (i.e logs, Binary trees, linked lists, configuration data, program state, etc). Edit: Also it could act as a shared memory location to.
Brynet-Inc wrote:
Not to mention it would use an excessive amount of resources...
Like the paging system, the resources would only be used when needed
Quote:
power failures would also make this idea a failure, and what about running multiple instances of the same application?
I'm assuming that when a process is terminated and can resume it's position when restarted? - How would you manage this? - Security concerns? proprietary API's?
These are problems I've yet to work out. Although, A MD5(or some sort of hash) could be used to manage data, this also would help prevent viruses.
Quote:
Even if this was possible, which I highly doubt.. you would be insane to try it.
it'd be very simple to implement, it would be incorporated into the paging subsystem. which when a program reads a particular address, the paging system loads the data from disk.