From 7d32deaea1de9eb9cd4816f94623b8f4b6243ee4 Mon Sep 17 00:00:00 2001 From: Fernando Luis Vazquez Cao Date: Tue, 29 Jul 2008 22:33:39 -0700 Subject: [PATCH] --- yaml --- r: 107020 b: refs/heads/master c: 7e6cbea39aaa32480145915751119227f29f6f7b h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/mm/madvise.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/[refs] b/[refs] index 83ce2a3af0aa..57c2df5ed4ce 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 641de9d8f505db055d451b50e6e38117f84e79bb +refs/heads/master: 7e6cbea39aaa32480145915751119227f29f6f7b diff --git a/trunk/mm/madvise.c b/trunk/mm/madvise.c index 23a0ec3e0ea0..f9349c18a1b5 100644 --- a/trunk/mm/madvise.c +++ b/trunk/mm/madvise.c @@ -132,10 +132,10 @@ static long madvise_willneed(struct vm_area_struct * vma, * Application no longer needs these pages. If the pages are dirty, * it's OK to just throw them away. The app will be more careful about * data it wants to keep. Be sure to free swap resources too. The - * zap_page_range call sets things up for refill_inactive to actually free + * zap_page_range call sets things up for shrink_active_list to actually free * these pages later if no one else has touched them in the meantime, * although we could add these pages to a global reuse list for - * refill_inactive to pick up before reclaiming other pages. + * shrink_active_list to pick up before reclaiming other pages. * * NB: This interface discards data rather than pushes it out to swap, * as some implementations do. This has performance implications for