Re: [BUGFIX][PATCH 3/4] mecg: fix oom flag at THP charge
From: Balbir Singh
Date: Mon Jan 31 2011 - 04:03:57 EST
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> [2011-01-28 17:21:46]:
> On Fri, 28 Jan 2011 09:02:13 +0100
> Johannes Weiner <hannes@xxxxxxxxxxx> wrote:
>
> > On Fri, Jan 28, 2011 at 12:27:29PM +0900, KAMEZAWA Hiroyuki wrote:
> > >
> > > Thanks to Johanns and Daisuke for suggestion.
> > > =
> > > Hugepage allocation shouldn't trigger oom.
> > > Allocation failure is not fatal.
> > >
> > > Orignal-patch-by: Johannes Weiner <hannes@xxxxxxxxxxx>
> > > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
> > > ---
> > > mm/memcontrol.c | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > Index: mmotm-0125/mm/memcontrol.c
> > > ===================================================================
> > > --- mmotm-0125.orig/mm/memcontrol.c
> > > +++ mmotm-0125/mm/memcontrol.c
> > > @@ -2369,11 +2369,14 @@ static int mem_cgroup_charge_common(stru
> > > struct page_cgroup *pc;
> > > int ret;
> > > int page_size = PAGE_SIZE;
> > > + bool oom;
> > >
> > > if (PageTransHuge(page)) {
> > > page_size <<= compound_order(page);
> > > VM_BUG_ON(!PageTransHuge(page));
> > > - }
> > > + oom = false;
> > > + } else
> > > + oom = true;
> >
> > That needs a comment. You can take the one from my patch if you like.
> >
>
> How about this ?
> ==
> Hugepage allocation shouldn't trigger oom.
> Allocation failure is not fatal.
>
Acked-by: Balbir Singh <balbir@xxxxxxxxxxxxxxxxxx>
--
Three Cheers,
Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/