The patch titled Subject: mm: do not drain pagevecs for mlockall(MCL_FUTURE) has been added to the -mm tree. Its filename is mm-do-not-drain-pagevecs-for-mlockallmcl_future.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/ ------------------------------------------------------ From: Christoph Lameter <cl@xxxxxxxxxx> Subject: mm: do not drain pagevecs for mlockall(MCL_FUTURE) MCL_FUTURE does not move pages between lru list and draining the LRU per cpu pagevecs is a nasty activity. Avoid doing it unecessarily. Signed-off-by: Christoph Lameter <cl@xxxxxxxxxx> Cc: David Rientjes <rientjes@xxxxxxxxxx> Reviewed-by: Minchan Kim <minchan.kim@xxxxxxxxx> Acked-by: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx> Cc: Mel Gorman <mel@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxx> --- mm/mlock.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff -puN mm/mlock.c~mm-do-not-drain-pagevecs-for-mlockallmcl_future mm/mlock.c --- a/mm/mlock.c~mm-do-not-drain-pagevecs-for-mlockallmcl_future +++ a/mm/mlock.c @@ -549,7 +549,8 @@ SYSCALL_DEFINE1(mlockall, int, flags) if (!can_do_mlock()) goto out; - lru_add_drain_all(); /* flush pagevec */ + if (flags & MCL_CURRENT) + lru_add_drain_all(); /* flush pagevec */ down_write(¤t->mm->mmap_sem); _ Subject: Subject: mm: do not drain pagevecs for mlockall(MCL_FUTURE) Patches currently in -mm which might be from cl@xxxxxxxxxx are origin.patch linux-next.patch mm-do-not-drain-pagevecs-for-mlockallmcl_future.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