> > Getting the user's "interactive" programs loaded back
> > in afterwards is a separate, much more difficult problem
> > IMHO, but no doubt still has a reasonable solution.
> Possibly stupid suggestion... Maybe the interactive/GUI programs should wake
> up once in a while and touch a couple of their pages? Go too far with this
> and you'll just get in the way of performance, but I don't think it would
> hurt to have processes waking up every couple of minutes and touching glibc,
> libqt, libgtk, etc so they stay hot in memory... A very slow incremental
> "caress" of the address space could eliminate the
Ugh... Ouch.... Ugly, indeed.
What you might want to do is
while true; do
cat /usr/lib/libc* > /dev/null; sleep 1m
cat /usr/lib/qt* > /dev/null; sleep 1m
running on your system...
-- Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt, details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/