Re: mmap behavior

This actually causes some trouble because my application relies on
vsize to perform some self-maintenance tasks.
With this fake 1GB overhead, this mechanism is broken.
Is there any workaround? Is there another way to reserve an address
space range for shared mappings?
Also, I could not find anything in /proc that would allow me to get the
"real" vsize.

Thanks,
Olivier.

.