[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHCio2i+HeB+LjqzjmQaqu7EnKOmSd4i4k73Kz2mt7bLqzw46A@mail.gmail.com>
Date: Mon, 4 Jun 2018 14:25:31 +0800
From: 禹舟键 <ufo19890607@...il.com>
To: rppt@...ux.vnet.ibm.com
Cc: akpm@...ux-foundation.org, mhocko@...e.com, rientjes@...gle.com,
kirill.shutemov@...ux.intel.com, aarcange@...hat.com,
penguin-kernel@...ove.sakura.ne.jp, guro@...com,
yang.s@...baba-inc.com, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Wind Yu <yuzhoujian@...ichuxing.com>
Subject: Re: [PATCH v7 2/2] Refactor part of the oom report in dump_header
Hi Mike
> My question was why do you call to alloc_constrained in the dump_header()
>function rather than pass the constraint that was detected a bit earlier to
>that function?
Ok, I will add a new parameter in the dump_header.
Thank you.
Powered by blists - more mailing lists