Memory Model

Discussions on more advanced topics such as monolithic vs micro-kernels, transactional memory models, and paging vs segmentation should go here. Use this forum to expand and improve the wiki!
Post Reply
cxzuk
Member
Member
Posts: 164
Joined: Mon Dec 21, 2009 6:03 pm

Memory Model

Post by cxzuk »

Hi all !

After much reading, im considering implementing Single-Level Store memory and was wondering if anyone else has tried implementing this or just general thoughts on it?

Mike Brown
--
http://en.wikipedia.org/wiki/Single-level_store

Single level store - RAM is basically ignored and is used as a cache, and memory is allocated from the hard drive.

The reasons why i like this is; with non-volatile RAM, and Solid State Drives - Memory "types" are merging. Fairly simple, Application's state can be stored in non-volatile memory and Filesystem structures are abstracted outside of raw storage.
ptr
Posts: 1
Joined: Tue May 03, 2011 12:24 am
Contact:

Re: Memory Model

Post by ptr »

Single-Level Store seems to be just one implementation of the concept of transparent persistence.

Transparent persistence has been implemented several times, most notably in the EROS operating system and its predecessor KeyKOS (but not in its successor Coyotos). The CapROS project continues development of the EROS codebase under the terms of the GPL. Additionally, there should be a number of papers, at least on EROS.

Transparent persistence is a nice concept. For example, there's no disk-ram-dichotomy (e.g. no need to remind yourself to periodically save your work) and you get hibernation for free (even in case of power failure, for example).
Post Reply