From: Johannes Weiner <jweiner@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrea Arcangeli <aarcange@redhat.com>,
linux-mm@kvack.org
Subject: Re: [patch v2] thp, memcg: split hugepage for memcg oom on cow
Date: Thu, 26 Apr 2012 11:06:42 +0200 [thread overview]
Message-ID: <20120426090642.GC1791@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204231612060.17030@chino.kir.corp.google.com>
[ Sorry, my responsiveness is horrible these days... ]
On Mon, Apr 23, 2012 at 04:15:06PM -0700, David Rientjes wrote:
> On Wed, 11 Apr 2012, Johannes Weiner wrote:
>
> > > diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> > > --- a/mm/huge_memory.c
> > > +++ b/mm/huge_memory.c
> > > @@ -950,6 +950,8 @@ int do_huge_pmd_wp_page(struct mm_struct *mm, struct vm_area_struct *vma,
> > > count_vm_event(THP_FAULT_FALLBACK);
> > > ret = do_huge_pmd_wp_page_fallback(mm, vma, address,
> > > pmd, orig_pmd, page, haddr);
> > > + if (ret & VM_FAULT_OOM)
> > > + split_huge_page(page);
> > > put_page(page);
> > > goto out;
> > > }
> > > @@ -957,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;
> > > diff --git a/mm/memory.c b/mm/memory.c
> > > --- a/mm/memory.c
> > > +++ b/mm/memory.c
> > > @@ -3489,6 +3489,7 @@ int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
> > > if (unlikely(is_vm_hugetlb_page(vma)))
> > > return hugetlb_fault(mm, vma, address, flags);
> > >
> > > +retry:
> > > pgd = pgd_offset(mm, address);
> > > pud = pud_alloc(mm, pgd, address);
> > > if (!pud)
> > > @@ -3502,13 +3503,24 @@ int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
> > > pmd, flags);
> > > } else {
> > > pmd_t orig_pmd = *pmd;
> > > + int ret;
> > > +
> > > barrier();
> > > if (pmd_trans_huge(orig_pmd)) {
> > > if (flags & FAULT_FLAG_WRITE &&
> > > !pmd_write(orig_pmd) &&
> > > - !pmd_trans_splitting(orig_pmd))
> > > - return do_huge_pmd_wp_page(mm, vma, address,
> > > - pmd, orig_pmd);
> > > + !pmd_trans_splitting(orig_pmd)) {
> > > + ret = do_huge_pmd_wp_page(mm, vma, address, pmd,
> > > + orig_pmd);
> > > + /*
> > > + * If COW results in an oom, the huge pmd will
> > > + * have been split, so retry the fault on the
> > > + * pte for a smaller charge.
> > > + */
> > > + if (unlikely(ret & VM_FAULT_OOM))
> > > + goto retry;
> >
> > Can you instead put a __split_huge_page_pmd(mm, pmd) here? It has to
> > redo the get-page-ref-through-pagetable dance, but it's more robust
> > and obvious than splitting the COW page before returning OOM in the
> > thp wp handler.
>
> I agree it's more robust if do_huge_pmd_wp_page() were modified later and
> mistakenly returned VM_FAULT_OOM without the page being split, but
> __split_huge_page_pmd() has the drawback of also requiring to retake
> mm->page_table_lock to test whether orig_pmd is still legitimate so it
> will be slower. Do you feel strongly about the way it's currently written
> which will be faster at runtime?
If you can't accomodate for a hugepage, this code runs 511 times in
the worst case before you also can't fit a regular page anymore. And
compare it to the cost of the splitting itself and the subsequent 4k
COW break faults...
I don't think it's a path worth optimizing for at all, especially if
it includes sprinkling undocumented split_huge_pages around, and the
fix could be as self-contained as something like this...
diff --git a/mm/memory.c b/mm/memory.c
index 706a274..dae0afc 100644
--- a/mm/memory.c
+++ b/mm/memory.c
@@ -3505,14 +3505,29 @@ int handle_mm_fault(struct mm_struct *mm, struct vm_area_struct *vma,
pmd, flags);
} else {
pmd_t orig_pmd = *pmd;
+ int ret;
+
barrier();
if (pmd_trans_huge(orig_pmd)) {
if (flags & FAULT_FLAG_WRITE &&
!pmd_write(orig_pmd) &&
- !pmd_trans_splitting(orig_pmd))
- return do_huge_pmd_wp_page(mm, vma, address,
+ !pmd_trans_splitting(orig_pmd)) {
+ ret = do_huge_pmd_wp_page(mm, vma, address,
pmd, orig_pmd);
- return 0;
+ if (unlikely(ret & VM_FAULT_OOM)) {
+ /*
+ * It's not worth going OOM
+ * over not being able to
+ * allocate or charge a full
+ * copy of the huge page.
+ * Split it up and handle as
+ * single page COW break below.
+ */
+ __split_huge_page_pmd(mm, pmd);
+ } else
+ return ret;
+ } else
+ return 0;
}
}
--
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-26 9:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-04 1:56 [patch] thp, memcg: split hugepage for memcg oom on cow David Rientjes
2012-04-09 9:10 ` KAMEZAWA Hiroyuki
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 [this message]
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=20120426090642.GC1791@redhat.com \
--to=jweiner@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.