The patch titled vmscan: fix get_scan_ratio() comment has been added to the -mm tree. Its filename is vmscan-fix-get_scan_ratio-comment.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: vmscan: fix get_scan_ratio() comment From: Rik van Riel <riel@xxxxxxxxxx> Fix the old comment on the scan ratio calculations. Signed-off-by: Rik van Riel <riel@xxxxxxxxxx> Cc: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- mm/vmscan.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff -puN mm/vmscan.c~vmscan-fix-get_scan_ratio-comment mm/vmscan.c --- a/mm/vmscan.c~vmscan-fix-get_scan_ratio-comment +++ a/mm/vmscan.c @@ -1389,9 +1389,9 @@ static void get_scan_ratio(struct zone * file_prio = 200 - sc->swappiness; /* - * anon recent_rotated[0] - * %anon = 100 * ----------- / ----------------- * IO cost - * anon + file rotate_sum + * The amount of pressure on anon vs file pages is inversely + * proportional to the fraction of recently scanned pages on + * each list that were recently referenced and in active use. */ ap = (anon_prio + 1) * (zone->recent_scanned[0] + 1); ap /= zone->recent_rotated[0] + 1; _ Patches currently in -mm which might be from riel@xxxxxxxxxx are vmscan-let-gfp_nofs-go-to-swap-again.patch vmscan-fix-get_scan_ratio-comment.patch linux-next.patch mm-more-likely-reclaim-madv_sequential-mappings.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html