Tweaks to madvise() and posix_fadvise()
Posted Feb 17, 2006 3:36 UTC (Fri) by email@example.com
Parent article: Tweaks to madvise() and posix_fadvise()
I think I'm missing a point, somewhere in the following para:
The copy-on-write operation described above will break the parent process's connection with the old page. But there is no way to inform the driver of that change. The result will be the situation shown on the right: the driver retains a reference to the page which now belongs exclusively to the child process(es). The parent process and the driver will no longer be able to communicate with each other.
Forgive my naivety, if there is something unstated that I _should have known_, but.. it seems to me that the parent/child haven't lost anything. They never _were_ able to actually communicate, were they? -- since neither could write something new and have it visible to the other.
to post comments)