Messages in this thread | | | Date | Thu, 12 Jan 2012 21:32:32 +0800 | Subject | Re: [PATCH] mm: vmscan: deactivate isolated pages with lru lock released | From | Hillf Danton <> |
| |
On Thu, Jan 12, 2012 at 10:28 AM, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote: > On Wed, 11 Jan 2012 20:45:07 +0800 > Hillf Danton <dhillf@gmail.com> wrote: > >> Spinners on other CPUs, if any, could take the lru lock and do their jobs while >> isolated pages are deactivated on the current CPU if the lock is released >> actively. And no risk of race raised as pages are already queued on locally >> private list. >> >> >> Signed-off-by: Hillf Danton <dhillf@gmail.com> > > Doesn't this increase the number of lock/unlock ? > Hmm, isn't it better to integrate clear_active_flags to isolate_pages() ? > Then we don't need list scan. > Look at it soon.
Thanks, Hillf
| |