> > > That would do it, but I was trying to give a real-world example from > image processing, like copying a large image file. Image processing people use tiling. Try loading a giant image into the gimp and into a non smart application like xpaint. The difference is huge just by careful implementation of the algorithms > Then the second pass will do an FFT on every column (row). The stride is > 16384*16 = 262144 bytes. This is a new page for each 16-byte complex > value you process :-). That is, all 16384 pages have to be in memory, or > swapped into memory if you've run out of real memory and the kernel has > swapped them out. Yes but you don't do it that way, you do stripes of parallel fft computations. We can all write dumb programs that don't behave well with the VM layer. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- RE: [2.4.17/18pre] VM and swap - it's really unusable"M. Edward Borasky" <znmeb _at_ aracnet.com>
- Re: [2.4.17/18pre] VM and swap - it's really unusable"M. Edward (Ed) Borasky" <znmeb _at_ aracnet.com>
- Prev by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by Date: Re: [PATCH] C undefined behavior fix
- Previous by thread: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by thread: RE: [2.4.17/18pre] VM and swap - it's really unusable
- Indexes:[Main][Thread]