[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHCio2hf-kfmVgz=KCvE9L4nPZxEVcFrxv2R1Y11etG=KvyBwg@mail.gmail.com>
Date: Thu, 5 Jul 2018 19:23:22 +0800
From: 禹舟键 <ufo19890607@...il.com>
To: mhocko@...nel.org
Cc: Andy Shevchenko <andy.shevchenko@...il.com>,
akpm@...ux-foundation.org, 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 v11 1/2] Refactor part of the oom report in dump_header
Hi Michal and Andy
The enum oom_constraint will be added in the struct oom_control. So
I still think I should define it in oom.h.
Michal Hocko <mhocko@...nel.org> 于2018年7月4日周三 下午4:17写道:
>
> On Wed 04-07-18 10:25:30, 禹舟键 wrote:
> > Hi Andy
> > The const char array need to be used by the new func
> > mem_cgroup_print_oom_context and some funcs in oom_kill.c in the
> > second patch.
>
> Just declare it in oom.h and define in oom.c
> --
> Michal Hocko
> SUSE Labs
Powered by blists - more mailing lists