Re: Copy-on-Write memory management
- From: Andrew Tomazos <andrew@xxxxxxxxxxx>
- Date: Sat, 25 Apr 2009 15:48:07 -0700 (PDT)
On Apr 26, 12:26 am, Michael Mol <mike...@xxxxxxxxx> wrote:
Let's say I wanted to implement a memory management system where I can
allocate a block of memory, write some data to it, and then clone it
in such a way that two separate pieces of code could own a copy of the
data, write to their copy, and when they read from their copy, they
saw their own written data there.
Now let's say that I want the clone operation to not result in an
increase in my footprint in the system memory until it was necessary
to write to the copy of the data.
Which operating systems, runtimes, libraries, architectures or
patterns have facilities which make this less difficult than it would
be without the facilities they provide?
(It's related to a performance-robustness balance problem I
occasionally encounter at work, but I'm mostly interested out of
personal curiosity; If my question seems ambiguous, it's because I'm
not looking for knowledge, not an exact solution.)
http://en.wikipedia.org/wiki/Copy_on_write
.
- Follow-Ups:
- Re: Copy-on-Write memory management
- From: Michael Mol
- Re: Copy-on-Write memory management
- References:
- Copy-on-Write memory management
- From: Michael Mol
- Copy-on-Write memory management
- Prev by Date: How much memory
- Next by Date: Re: doing things with binary trees
- Previous by thread: Copy-on-Write memory management
- Next by thread: Re: Copy-on-Write memory management
- Index(es):
Relevant Pages
|