Messages in this thread Patch in this message | | | From | KOSAKI Motohiro <> | Subject | Re: [PATCH] vmscan: bail out of page reclaim after swap_cluster_max pages | Date | Wed, 26 Nov 2008 11:24:52 +0900 (JST) |
| |
> + /* > + * On large memory systems, scan >> priority can become > + * really large. This is fine for the starting priority; > + * we want to put equal scanning pressure on each zone. > + * However, if the VM has a harder time of freeing pages, > + * with multiple processes reclaiming pages, the total > + * freeing target can get unreasonably large. > + */ > + if (sc->nr_reclaimed > sc->swap_cluster_max && > + sc->priority < DEF_PRIORITY && !current_is_kswapd()) > + break;
typo. this patch can't compile.
--- mm/vmscan.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Index: b/mm/vmscan.c =================================================================== --- a/mm/vmscan.c +++ b/mm/vmscan.c @@ -1469,7 +1469,7 @@ static void shrink_zone(int priority, st * freeing target can get unreasonably large. */ if (sc->nr_reclaimed > sc->swap_cluster_max && - sc->priority < DEF_PRIORITY && !current_is_kswapd()) + priority < DEF_PRIORITY && !current_is_kswapd()) break; }
| |