Paul J. Lucas writes:
On Fri, 28 Jul 2000, Malcolm Beattie wrote:
Assuming the kernel only keeps track of the last fault position in the file,
it won't recognise that it's being read linearly (twice :-) and may well not
do the async read ahead and drop behind in page cache that it would
On Fri, 28 Jul 2000, Kenneth Lee wrote:
it would be good for the user to choose between mmap or normal i/o at
compile time. i'll try HTML::Tree anyway in the meantime.
It's not that simple. Using mmap(2) greatly affects how one
writes code: it's not a drop-in replacement for
On Fri, 28 Jul 2000, Paul J. Lucas wrote:
On Fri, 28 Jul 2000, Kenneth Lee wrote:
it would be good for the user to choose between mmap or normal i/o at
compile time. i'll try HTML::Tree anyway in the meantime.
It's not that simple. Using mmap(2) greatly affects how one
Paul J. Lucas writes:
This is the quote from "Philip and Alex..." that I was talking about
earlier. I don't know if its relevant or not:
They replied "NaviServer uses memory-mapped file I/O on single-processor
machines but automatically configures itself to use operating system read on
On Fri, 28 Jul 2000, Malcolm Beattie wrote:
Assuming the kernel only keeps track of the last fault position in the file,
it won't recognise that it's being read linearly (twice :-) and may well not
do the async read ahead and drop behind in page cache that it would do
otherwise. Once again,
