[PATCH v2] memcg: reduce lock time at move charge (Was Re: [PATCH 04/10] memcg: disable local interrupts in lock_page_cgroup()
balbir at linux.vnet.ibm.com
Mon Oct 11 20:39:15 PDT 2010
* KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> [2010-10-08 19:41:31]:
> On Fri, 8 Oct 2010 14:12:01 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com> wrote:
> > > Sure. It walks the same data three times, potentially causing
> > > thrashing in the L1 cache.
> > Hmm, make this 2 times, at least.
> How about this ?
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu at jp.fujitsu.com>
> Presently, at task migration among cgroups, memory cgroup scans page tables and
> moves accounting if flags are properly set.
> The core code, mem_cgroup_move_charge_pte_range() does
> 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()
> for pte entries on a 3rd level? page table.
> As a planned updates, we'll support dirty-page accounting. Because move_charge()
> is highly race, we need to add more check in move_charge.
> For example, lock_page();-> wait_on_page_writeback();-> unlock_page();
> is an candidate for new check.
Is this a change to help dirty limits or is it a generic bug fix.
More information about the Containers