It does. I wonder who the culprit was that removed the state = 0
from 2.1.129 -> 2.1.130? We've had the state = 0 since 2.1.90
when we put it in...
> >--- mm/vmscan.c.~1~ Mon Dec 7 12:05:54 1998
> >+++ mm/vmscan.c Mon Dec 7 18:55:55 1998
> >@@ -432,6 +432,8 @@
> >
> > if (buffer_over_borrow() || pgcache_over_borrow())
> > state = 0;
> >+ if (atomic_read(&nr_async_pages) > pager_daemon.swap_cluster / 2)
> >+ shrink_mmap(i, gfp_mask);
> >
>
> Doing that we risk to shrink too much cache even if not necessary
> but this part of the patch improve a _lot_ swapping performance even
> if I don' t know why ;)
This is because 'swapped' data is added to the cache. It also
is because without it kswapd would not free memory in swap_out().
Then, because it didn't free memory, it would continue to swap
out more and more and still more with no effect (remember the
removal of page aging?).
All this is fixed by the two little lines above :)
> And why not to use GFP_USER in the userspace swaping code?
> if (found_page)
> goto out;
>
> - new_page_addr = __get_free_page(GFP_KERNEL);
> + new_page_addr = __get_free_page(GFP_USER);
> if (!new_page_addr)
> goto out; /* Out of memory */
> new_page = mem_map + MAP_NR(new_page_addr);
Seems like a great idea... Stephen?
cheers,
Rik -- the flu hits, the flu hits, the flu hits -- MORE
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/