Re: mmapping large files hits swap in 2.4?

[Richard Zidlicky <rz@linux-m68k.org>]

On Sat, Aug 10, 2002 at 06:17:25PM +0200, Daniel Egger wrote:
> Am Sam, 2002-08-10 um 14.12 schrieb Richard Zidlicky:
> 
> > seems like you are doing something else, like hitting all
> > of the file.
>  
> > # uname -a
> > Linux sirizidl.dialin.rrze.uni-erlangen.de 2.4.18 #27 Wed Jul 24 17:25:39 CEST 2002 m68k unknown
>  
> > main()
> > {
> >   char *area;
> >   int fd=open("/msrc/linux/distr/cd.image", O_RDWR);
> >   area = mmap (0, 168088*4096, PROT_READ | PROT_WRITE, MAP_SHARED, fd, 0);
> >   if (area == -1) perror("mmap");
> > }
> 
> Heh. Well of course I'm also trying to use the memory I mmaped. :)
> It is just that it seems the mmaped region is not really bakked by
> the underlying file but by swap space which was exactly what I 
> was trying to avoid by using a file.

still works as expected for me, accessing a 650 MB file with only 
about 350 MB swap is no problem. It takes some time on that old
m68k box but clearly dominated by HD read time.. a compilation 
runing in the background doesn't seem to make any difference
at all.

Richard