>     There seem to be some misconceptions about what we are really
>     doing.  We map a shared(*1), read-only copy of the file into
>     our address space, we don't allocate any memory, we don't
>     operate on the mmap'ed area, and this does not change when
>     you "add headers or do something else to really large files".

Yes, I didn't understand the underlying nature of mmap correctly.  After
Thies' message yesterday I did some reading and agree with you.  The mmap
approach is good provided the OS doesn't screw up along the way.


PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]

Reply via email to