On 2007-01-03, Hans-Werner Hilse <[EMAIL PROTECTED]> wrote:
>> You don't think that 58M of virtual memory usage isn't a
>> resource hog when the X server only requires 56M and the next
>> largest program is 32M? Virtual memory _is_ a resource,
>> though not an expensive one.
>
> Errrm, to get back to my example above: Mmap'ing a file (and increasing
> your programs VSZ) is often much more elegant than classic procedural
> fseek'ing and fread'ing. Nothing, absolutely nothing makes that causing
> the program to become a "resource hog". The VM subsystem will care that
> exactly those parts of the file will be cached, buffered, accessed and
> (if needed) copied that are used.
You're right. For some reason I was thinking that that virtual
memory was taking up swap space, but it's almost certainly just
read-only pages that never hit swap at all.
--
Grant Edwards grante Yow! Is this TERMINAL fun?
at
visi.com
--
[email protected] mailing list
