From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <jweiner@redhat.com>,
linux-mm@kvack.org
Subject: Re: [patch] thp, memcg: split hugepage for memcg oom on cow
Date: Mon, 09 Apr 2012 18:10:21 +0900 [thread overview]
Message-ID: <4F82A77D.4020800@jp.fujitsu.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204031854530.30629@chino.kir.corp.google.com>
(2012/04/04 10:56), David Rientjes wrote:
> On COW, a new hugepage is allocated and charged to the memcg. If the
> memcg is oom, however, this charge will fail and will return VM_FAULT_OOM
> to the page fault handler which results in an oom kill.
>
> Instead, it's possible to fallback to splitting the hugepage so that the
> COW results only in an order-0 page being charged to the memcg which has
> a higher liklihood to succeed. This is expensive because the hugepage
> must be split in the page fault handler, but it is much better than
> unnecessarily oom killing a process.
>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> mm/huge_memory.c | 1 +
> mm/memory.c | 18 +++++++++++++++---
> 2 files changed, 16 insertions(+), 3 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -959,6 +959,7 @@ int do_huge_pmd_wp_page(struct mm_struct *mm, struct vm_area_struct *vma,
>
> if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL))) {
> put_page(new_page);
> + split_huge_page(page);
> put_page(page);
> ret |= VM_FAULT_OOM;
> goto out;
?? how about
==
if (transparent_hugepage_enabled(vma) &&
!transparent_hugepage_debug_cow())
new_page = alloc_hugepage_vma(transparent_hugepage_defrag(vma),
vma, haddr, numa_node_id(), 0);
else
new_page = NULL;
if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL))) {
put_page(new_page);
new_page = NULL; /* never OOM, just cause fallback */
}
if (unlikely(!new_page)) {
count_vm_event(THP_FAULT_FALLBACK);
ret = do_huge_pmd_wp_page_fallback(mm, vma, address,
pmd, orig_pmd, page, haddr);
put_page(page);
goto out;
}
==
?
Thanks,
-Kame
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-09 9:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 1:56 David Rientjes
2012-04-09 9:10 ` KAMEZAWA Hiroyuki [this message]
2012-04-10 0:23 ` David Rientjes
2012-04-10 0:43 ` KAMEZAWA Hiroyuki
2012-04-10 0:49 ` KAMEZAWA Hiroyuki
2012-04-10 5:41 ` David Rientjes
2012-04-10 5:42 ` [patch v2] " David Rientjes
2012-04-10 5:59 ` KAMEZAWA Hiroyuki
2012-04-11 14:20 ` Johannes Weiner
2012-04-23 23:15 ` David Rientjes
2012-04-25 21:01 ` David Rientjes
2012-04-26 9:06 ` Johannes Weiner
2012-04-26 21:05 ` David Rientjes
2012-04-27 0:15 ` Johannes Weiner
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=4F82A77D.4020800@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=jweiner@redhat.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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