* [PATCH v2] mm, memcg: add a helper function to check may oom condition
@ 2013-09-10 1:24 Qiang Huang
2013-09-10 6:34 ` David Rientjes
0 siblings, 1 reply; 2+ messages in thread
From: Qiang Huang @ 2013-09-10 1:24 UTC (permalink / raw)
To: Andrew Morton
Cc: Michal Hocko, hannes, Li Zefan, Cgroups, linux-mm, David Rientjes
Use helper function to check if we need to deal with oom condition.
v2:
Change the function name to oom_gfp_allowed() as suggested by
David Rientjes.
Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
---
include/linux/oom.h | 5 +++++
mm/memcontrol.c | 9 +--------
mm/page_alloc.c | 2 +-
3 files changed, 7 insertions(+), 9 deletions(-)
diff --git a/include/linux/oom.h b/include/linux/oom.h
index da60007..4cd6267 100644
--- a/include/linux/oom.h
+++ b/include/linux/oom.h
@@ -82,6 +82,11 @@ static inline void oom_killer_enable(void)
oom_killer_disabled = false;
}
+static inline bool oom_gfp_allowed(gfp_t gfp_mask)
+{
+ return (gfp_mask & __GFP_FS) && !(gfp_mask & __GFP_NORETRY);
+}
+
extern struct task_struct *find_lock_task_mm(struct task_struct *p);
/* sysctls */
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index b73988a..392e668 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2910,21 +2910,14 @@ static int memcg_charge_kmem(struct mem_cgroup *memcg, gfp_t gfp, u64 size)
struct res_counter *fail_res;
struct mem_cgroup *_memcg;
int ret = 0;
- bool may_oom;
ret = res_counter_charge(&memcg->kmem, size, &fail_res);
if (ret)
return ret;
- /*
- * Conditions under which we can wait for the oom_killer. Those are
- * the same conditions tested by the core page allocator
- */
- may_oom = (gfp & __GFP_FS) && !(gfp & __GFP_NORETRY);
-
_memcg = memcg;
ret = __mem_cgroup_try_charge(NULL, gfp, size >> PAGE_SHIFT,
- &_memcg, may_oom);
+ &_memcg, oom_gfp_allowed(gfp));
if (ret == -EINTR) {
/*
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index b7c612d..079ee3d 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -2589,7 +2589,7 @@ rebalance:
* running out of options and have to consider going OOM
*/
if (!did_some_progress) {
- if ((gfp_mask & __GFP_FS) && !(gfp_mask & __GFP_NORETRY)) {
+ if (oom_gfp_allowed(gfp_mask)) {
if (oom_killer_disabled)
goto nopage;
/* Coredumps can quickly deplete all memory reserves */
--
1.8.3
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH v2] mm, memcg: add a helper function to check may oom condition
2013-09-10 1:24 [PATCH v2] mm, memcg: add a helper function to check may oom condition Qiang Huang
@ 2013-09-10 6:34 ` David Rientjes
0 siblings, 0 replies; 2+ messages in thread
From: David Rientjes @ 2013-09-10 6:34 UTC (permalink / raw)
To: Qiang Huang
Cc: Andrew Morton, Michal Hocko, hannes, Li Zefan, Cgroups, linux-mm
On Tue, 10 Sep 2013, Qiang Huang wrote:
> Use helper function to check if we need to deal with oom condition.
>
> v2:
> Change the function name to oom_gfp_allowed() as suggested by
> David Rientjes.
>
> Signed-off-by: Qiang Huang <h.huangqiang@huawei.com>
Acked-by: David Rientjes <rientjes@google.com>
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-09-10 6:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-10 1:24 [PATCH v2] mm, memcg: add a helper function to check may oom condition Qiang Huang
2013-09-10 6:34 ` David Rientjes
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox