apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <...@covalent.net>
Subject Re: file_setaside()
Date Tue, 26 Jun 2001 15:48:28 GMT

> > Sooner or later, we are going to be writing the file someplace.  That
> > could be the network, or it could be into memory to do some mucking with
> > the data.  Since we are either dup'ing it or mmap'ing it, I figured we
> > could be conservative here and mmap the data.  If we dup it here, and then
> > have to read, then we have dup'ed and mmap'ed.  This way, we only mmap the
> > data.
> The setaside() could be called on *really* large files. Calling mmap could
> be a very bad thing. Just dup the FILE bucket and leave it at that. The
> decision to do the mmap can/should come when it becomes necessary.

Why is calling mmap on a large file a bad thing?


Ryan Bloom                        	rbb@apache.org
Covalent Technologies			rbb@covalent.net

View raw message