All this talk about "overcommitting memory" confuses, at least in the text,
"memory" with "address space".

The 4.4BSD VM (and some others, if I read the thread right) allows to seperate
the two.

To the very least, please don't mention sbrk() again. It's just a special
case of an unnamed mmap(), for our VM systems..

This might be the reason why bookkeeping, and limiting, of the real swap
needed, is more difficult than it used to be. A 2nd problem is, that pages
might be shared between processes.... even unnamed mmap() regions, if I read
the mmap(2) man page right...

Regards,
	-is