From: Michal Hocko <mhocko@kernel.org>
To: James Morse <james.morse@arm.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov@virtuozzo.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Subject: Re: [PATCH] mm: memcontrol: Make the walk_page_range() limit obvious
Date: Wed, 31 Aug 2016 17:17:30 +0200 [thread overview]
Message-ID: <20160831151730.GF21661@dhcp22.suse.cz> (raw)
In-Reply-To: <1472655897-22532-1-git-send-email-james.morse@arm.com>
On Wed 31-08-16 16:04:57, James Morse wrote:
> Trying to walk all of virtual memory requires architecture specific
> knowledge. On x86_64, addresses must be sign extended from bit 48,
> whereas on arm64 the top VA_BITS of address space have their own set
> of page tables.
>
> mem_cgroup_count_precharge() and mem_cgroup_move_charge() both call
> walk_page_range() on the range 0 to ~0UL, neither provide a pte_hole
> callback, which causes the current implementation to skip non-vma regions.
>
> As this call only expects to walk user address space, make it walk
> 0 to 'highest_vm_end'.
>
> Signed-off-by: James Morse <james.morse@arm.com>
> Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> ---
> This is in preparation for a RFC series that allows walk_page_range() to
> walk kernel page tables too.
OK, so do I get it right that this is only needed with that change?
Because AFAICS walk_page_range will be bound to the last vma->vm_end
right now. If this is the case this should be mentioned in the changelog
because the above might confuse somebody to think this is a bug fix.
Other than that this seams reasonable to me.
>
> mm/memcontrol.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index 2ff0289ad061..bfd54b43beb9 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -4712,7 +4712,8 @@ static unsigned long mem_cgroup_count_precharge(struct mm_struct *mm)
> .mm = mm,
> };
> down_read(&mm->mmap_sem);
> - walk_page_range(0, ~0UL, &mem_cgroup_count_precharge_walk);
> + walk_page_range(0, mm->highest_vm_end,
> + &mem_cgroup_count_precharge_walk);
> up_read(&mm->mmap_sem);
>
> precharge = mc.precharge;
> @@ -5000,7 +5001,8 @@ retry:
> * When we have consumed all precharges and failed in doing
> * additional charge, the page walk just aborts.
> */
> - walk_page_range(0, ~0UL, &mem_cgroup_move_charge_walk);
> + walk_page_range(0, mc.mm->highest_vm_end, &mem_cgroup_move_charge_walk);
> +
> up_read(&mc.mm->mmap_sem);
> atomic_dec(&mc.from->moving_account);
> }
> --
> 2.8.0.rc3
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-08-31 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 15:04 [PATCH] mm: memcontrol: Make the walk_page_range() limit obvious James Morse
2016-08-31 15:17 ` Michal Hocko [this message]
2016-09-01 0:24 ` Naoya Horiguchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160831151730.GF21661@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=james.morse@arm.com \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vdavydov@virtuozzo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).