Re: Thread implementations...

Chris Wedgwood (chris@cybernet.co.nz)
Fri, 26 Jun 1998 09:24:30 +1200

> Not necessarily; we may be able to detect a lot of the relevant access
> patterns ourselves. Ingo has had a swap prediction algorithm for a
> while, and we talked at Usenix about a number of other things we can do
> to tune vm performance automatically. 2.3 ought to be a great deal
> better. madvise() may still have merit, but we really ought to be
> aiming at making the vm system as self-tuning as possible.

madvise(2) will _always_ have some uses.

Large database applications and stuff can know in advance how to tune mmap
regions and stuff. The kernel will always be second guessing here, and
making sub optimal decisions, whereas the application can and probably does
know better.

The same argument also applies to raw devices (but lets not start that
thread again).

-Chris

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu