[<prev] [next>] [day] [month] [year] [list]
Message-ID: <048701d066d2$86b182d0$94148870$@alibaba-inc.com>
Date: Wed, 25 Mar 2015 16:05:57 +0800
From: "Hillf Danton" <hillf.zj@...baba-inc.com>
To: "Johannes Weiner" <hannes@...xchg.org>
Cc: "linux-kernel" <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, "Hillf Danton" <hillf.zj@...baba-inc.com>
Subject: Re: [patch 06/12] mm: oom_kill: simplify OOM killer locking
> --- a/include/linux/oom.h
> +++ b/include/linux/oom.h
> @@ -32,6 +32,8 @@ enum oom_scan_t {
> /* Thread is the potential origin of an oom condition; kill first on oom */
> #define OOM_FLAG_ORIGIN ((__force oom_flags_t)0x1)
>
> +extern struct mutex oom_lock;
> +
> static inline void set_current_oom_origin(void)
> {
> current->signal->oom_flags |= OOM_FLAG_ORIGIN;
> @@ -60,9 +62,6 @@ extern void oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
> struct mem_cgroup *memcg, nodemask_t *nodemask,
> const char *message);
>
> -extern bool oom_zonelist_trylock(struct zonelist *zonelist, gfp_t gfp_flags);
> -extern void oom_zonelist_unlock(struct zonelist *zonelist, gfp_t gfp_flags);
Alternately expose three functions, rather than oom_lock mutex?
bool oom_trylock(void);
void oom_lock(void);
void oom_unlock(void);
Hillf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists