[Devel] Re: [PATCH v2] memcg: reduce lock time at move charge (Was Re: [PATCH 04/10] memcg: disable local interrupts in lock_page_cgroup()
KAMEZAWA Hiroyuki
kamezawa.hiroyu at jp.fujitsu.com
Thu Oct 7 22:12:01 PDT 2010
On Thu, 7 Oct 2010 21:55:56 -0700
Andrew Morton <akpm at linux-foundation.org> wrote:
> On Fri, 8 Oct 2010 13:37:12 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
>
> > On Thu, 7 Oct 2010 16:14:54 -0700
> > Andrew Morton <akpm at linux-foundation.org> wrote:
> >
> > > On Thu, 7 Oct 2010 17:04:05 +0900
> > > KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > >
> > > > Now, at task migration among cgroup, memory cgroup scans page table and moving
> > > > account if flags are properly set.
> > > >
> > > > The core code, mem_cgroup_move_charge_pte_range() does
> > > >
> > > > pte_offset_map_lock();
> > > > for all ptes in a page table:
> > > > 1. look into page table, find_and_get a page
> > > > 2. remove it from LRU.
> > > > 3. move charge.
> > > > 4. putback to LRU. put_page()
> > > > pte_offset_map_unlock();
> > > >
> > > > for pte entries on a 3rd level? page table.
> > > >
> > > > This pte_offset_map_lock seems a bit long. This patch modifies a rountine as
> > > >
> > > > for 32 pages: pte_offset_map_lock()
> > > > find_and_get a page
> > > > record it
> > > > pte_offset_map_unlock()
> > > > for all recorded pages
> > > > isolate it from LRU.
> > > > move charge
> > > > putback to LRU
> > > > for all recorded pages
> > > > put_page()
> > >
> > > The patch makes the code larger, more complex and slower!
> > >
> >
> > Slower ?
>
> Sure. It walks the same data three times, potentially causing
> thrashing in the L1 cache.
Hmm, make this 2 times, at least.
> It takes and releases locks at a higher frequency. It increases the text size.
>
But I don't think page_table_lock is a lock which someone can hold so long
that
1. find_get_page
2. spin_lock(zone->lock)
3. remove it from LRU
4. lock_page_cgroup()
5. move charge (This means page
5. putback to LRU
for 4096/8=1024 pages long.
will try to make the routine smarter.
But I want to get rid of page_table_lock -> lock_page_cgroup().
Thanks,
-Kame
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers
More information about the Devel
mailing list