One of the problems with the whole virtual memory overcommit issue is the difficulty of working out how much memorytruly is committed. For example, consider all of the ways that Unixkernels can commit themselves to holding down memory on behalf of a userprocess. In addition to obvious things like System V shared memory, thisincludes (but isn't limited to):

• pipe data buffers, including unused ones; theoretically every pipepair created commits the kernel to at least 4K of buffer or so.
• socket send and

One of the things that irritates me about commercial support is the difficulty of getting a definite answerfrom them if they do not have a canned solution to my issue. If theycannot give me great news, getting any news from them is often likepulling teeth (or slower), and even when they're willing to talk to methey tend to mumble a lot.

I want answers for a simple reason: it lets me resolve the situationone way or another. In this, I would rather have a