That would solve _your_ problem. But lots of other people
would get another problem - much _more_ swapping:
Whenever they quit one big app to run another big one,
everything is pulled in from swap before the next
big app start. Then it starts, and push everything out
again. The current system lets you quit one app,
the stuff in swap remains there until someone actually use it,
and lots of free memory remain in case it is needed.
The "intelligent" thing is to leave stuff in swap until
some app needs it, and pull it in then. Perhaps with
some read-ahead/clustering to minimize io load.
It is simply impossible to know "what" the
next thing we will need from swap will be, and what
stuff won't ever be needed from swap. The memory
might be putr to better uses, such as:
1. New programs/allocations can start without
having to push something out first
2. file cache for io-intensive apps.
Note that reading from swap is very much like reading
from executable files - it is done when needed.
We donŠ't normally pre-read every executable
on the system when there is free memory just
in case someone might want to run a program,
the same applies to swap.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/