Re: Memory-mapped files

2002-11-13 Thread M. Gerards
> This is kind of annoying because implementing io_map on the server side in > not > necessarily trivial I think. How can this be implemented in a server that > doesn't use libpager (I don't think there are such examples in the source > tree)? It is easy to add. I one wrote a small test program t

Re: Memory-mapped files

2002-11-12 Thread Marcus Brinkmann
On Tue, Nov 12, 2002 at 06:21:04PM +0100, Ludovic Courtès wrote: > On Tue, Nov 12, 2002 at 01:41:47PM +0100, Marcus Brinkmann wrote: > > They should fall back to normal read/write if mmap fails. > > Gcc does not actually fall back to normal read/write. Should we ask them to > fix that? I think t

Re: Memory-mapped files

2002-11-12 Thread Ludovic Courtès
On Tue, Nov 12, 2002 at 01:41:47PM +0100, Marcus Brinkmann wrote: > They should fall back to normal read/write if mmap fails. Gcc does not actually fall back to normal read/write. Should we ask them to fix that? > Why can't you use libpager? This is a netfs-based filesystem (tarfs). So far, I'

Re: Memory-mapped files

2002-11-12 Thread Niels Möller
"Ludovic Courtès" <[EMAIL PROTECTED]> writes: > Although the GNU Coding Standards specify that user applications shouldn't > rely on mmap() to read files, it turns out that gcc sometimes relies on it > (depending on the source file size I think). Should we ask the gcc team to > change that? ;) g

Re: Memory-mapped files

2002-11-12 Thread Marcus Brinkmann
On Tue, Nov 12, 2002 at 10:59:16AM +0100, Ludovic Courtès wrote: > Hi, > > Although the GNU Coding Standards specify that user applications shouldn't > rely on mmap() to read files, it turns out that gcc sometimes relies on it > (depending on the source file size I think). Should we ask the gcc t

Memory-mapped files

2002-11-12 Thread Ludovic Courtès
Hi, Although the GNU Coding Standards specify that user applications shouldn't rely on mmap() to read files, it turns out that gcc sometimes relies on it (depending on the source file size I think). Should we ask the gcc team to change that? ;) This is kind of annoying because implementing io_ma