Show memcg information during OOM
Subsystems (3)
PATCH 1/1 Show memcg information during OOM
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
From: Balbir Singh <[email protected]>
Description: Add RSS and swap to OOM output from memcg
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
---
include/linux/memcontrol.h | 5 +++++ mm/memcontrol.c | 15 +++++++++++++++ mm/oom_kill.c | 1 + 3 files changed, 21 insertions(+), 0 deletions(-)
include/linux/memcontrol.h +5 -0
@@ -104,6 +104,7 @@ struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat(struct mem_cgroup *memcg, struct zone *zone);struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat_from_page (struct page *page); +extern void mem_cgroup_print_mem_info (struct mem_cgroup *memcg);#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP extern int do_swap_account;
@@ -270,6 +271,10 @@ mem_cgroup_get_reclaim_stat_from_page(struct page *page)return NULL ; } +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +} +#endif /* CONFIG_CGROUP_MEM_CONT */ #endif /* _LINUX_MEMCONTROL_H */
mm/memcontrol.c +15 -0
@@ -813,6 +813,21 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked.
mm/oom_kill.c +1 -0
@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);task_unlock (current);dump_stack ();show_mem ();
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Hi
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 828
Quoted 12 lines
mm/memcontrol.c +12
-0+void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));
s/res/memsw/ ?
and, I don't like the name of "Memory cgroup RSS" and "Memory cgroup swap". it seems misleading. memcg->res doesn't only count count rss, but also cache. memcg->memsw doesn't only count swap, but also memory.
otherthing, I think it is good patch for me :)
Quoted 26 lines
mm/memcontrol.c +2
-0+} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked. mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);task_unlock (current);dump_stack ();show_mem ();Signature · 8 lines
-- Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 17 lines · KOSAKI Motohiro
Hi
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 828
Quoted 12 lines
mm/memcontrol.c +12
-0+void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));s/res/memsw/ ?
Quoted 6 lines
and, I don't like the name of "Memory cgroup RSS" and "Memory cgroup swap". it seems misleading.
memcg->resdoesn't only count count rss, but also cache.memcg->memswdoesn't only count swap, but also memory.otherthing, I think it is good patch for me :)
Good point, I fixed the res/memsw problem and sent out a patch. About the RSS thing, not sure what to call it, just calling it memory can be confusing, may be I should call it
Memory and Memory+swap
Thanks for the review
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 15 lines · KOSAKI Motohiro
Hi
Review
Quoted 12 lines
(quoted diff) +12
-0+void mem_cgroup_print_mem_info(struct mem_cgroup *memcg) +{ + printk(KERN_WARNING "Memory cgroups's name %s\n", + memcg->css.cgroup->dentry->d_name.name); + printk(KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" + " failcnt %llu\n", res_counter_read_u64(&memcg->res, RES_USAGE), + res_counter_read_u64(&memcg->res, RES_LIMIT), + res_counter_read_u64(&memcg->res, RES_FAILCNT)); + printk(KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " + "failcnt %llu\n", res_counter_read_u64(&memcg->res, RES_USAGE), + res_counter_read_u64(&memcg->res, RES_LIMIT), + res_counter_read_u64(&memcg->res, RES_FAILCNT));
Thanks! How does this look
Description: Add RSS and swap to OOM output from memcg
From: Balbir Singh <[email protected]>
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
Thanks go out to Johannes Weiner <[email protected]> and KOSAKI Motohiro <[email protected]> for review.
---
include/linux/memcontrol.h | 5 +++++ mm/memcontrol.c | 19 +++++++++++++++++++ mm/oom_kill.c | 1 + 3 files changed, 25 insertions(+), 0 deletions(-)
include/linux/memcontrol.h +5 -0
@@ -104,6 +104,7 @@ struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat(struct mem_cgroup *memcg, struct zone *zone);struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat_from_page (struct page *page); +extern void mem_cgroup_print_mem_info (struct mem_cgroup *memcg);#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP extern int do_swap_account;
@@ -270,6 +271,10 @@ mem_cgroup_get_reclaim_stat_from_page(struct page *page)return NULL ; } +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +} +#endif /* CONFIG_CGROUP_MEM_CONT */ #endif /* _LINUX_MEMCONTROL_H */
mm/memcontrol.c +19 -0
@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked.
mm/oom_kill.c +1 -0
@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);task_unlock (current);dump_stack ();show_mem ();
Signature · 1 line
Balbir
David Rientjes
reviewerQuoted 20 lines · Balbir Singh
mm/memcontrol.c +12
-0@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 837
Quoted 10 lines
mm/memcontrol.c +7
-0+printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked.
I think you'd want a less critical log level for these messages such as KERN_INFO.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 5 lines · David Rientjes
On Mon, 2 Feb 2009, Balbir Singh wrote:
I think you'd want a less critical log level for these messages such as
KERN_INFO.
David, I'd agree, but since we are under printk_ratelimit() and this is a not-so-common path, does the log level matter much? If it does, I don't mind using KERN_INFO.
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
David Rientjes
reviewerQuoted 4 lines · Balbir Singh
David, I'd agree, but since we are under
printk_ratelimit()and this is a not-so-common path, does the log level matter much? If it does, I don't mind usingKERN_INFO.
It matters for parsing dmesg output; the only KERN_WARNING message from the oom killer is normally the header. There's a couple extra ones for error conditions (that could certainly be changed to KERN_ERR), but only in very rare circumstances.
As defined by include/linux/kernel.h:
#define KERN_WARNING "<4>" /* warning conditions */ ... #define KERN_INFO "<6>" /* informational */
The meminfo you are printing falls under the "informational" category, no?
While you're there, it might also be helpful to make another change that would also help in parsing the output:
Quoted 6 lines
mm/memcontrol.c +0
-0@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 823
Quoted 10 lines
mm/memcontrol.c +8
-0return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name);
This should be "cgroup's", but I don't think you want to print this on a line by itself since the only system-wide synchronization here is a read-lock on tasklist_lock and there could be two separate memcg's that are oom.
So it's quite possible, though unlikely, that two seperate oom events would have these messages merged together in the ring buffer, which would make parsing impossible.
I think you probably want to add the name to each line you print, such as:
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 827
Quoted 4 lines
mm/memcontrol.c +4
-0+printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));
const char *name = memcg->css.cgroup->dentry->d_name.name; printk(KERN_INFO "Cgroup %s memory: usage %llu, limit %llu" " failcount %llu\n", name, ...);
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 832
Quoted 5 lines
mm/memcontrol.c +5
-0+printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT ));
and
printk(KERN_INFO "Cgroup %s memory+swap: usage %llu, limit %llu " "failcnt %llu\n", name, ...);
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 833
Quoted 1 line
mm/memcontrol.c +1
-0+}
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 69 lines · David Rientjes
Quoted 4 lines · Balbir Singh
David, I'd agree, but since we are under
printk_ratelimit()and this is a not-so-common path, does the log level matter much? If it does, I don't mind usingKERN_INFO.It matters for parsing dmesg output; the only
KERN_WARNINGmessage from the oom killer is normally the header. There's a couple extra ones for error conditions (that could certainly be changed toKERN_ERR), but only in very rare circumstances.As defined by
include/linux/kernel.h:#define KERN_WARNING "<4>" /* warning conditions */ ... #define KERN_INFO "<6>" /* informational */The meminfo you are printing falls under the "informational" category, no?
While you're there, it might also be helpful to make another change that would also help in parsing the output:
Quoted 6 lines
mm/memcontrol.c +0
-0@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 823
Quoted 10 lines
mm/memcontrol.c +8
-0return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name);This should be "cgroup's", but I don't think you want to print this on a line by itself since the only system-wide synchronization here is a read-lock on
tasklist_lockand there could be two separate memcg's that are oom.So it's quite possible, though unlikely, that two seperate oom events would have these messages merged together in the ring buffer, which would make parsing impossible.
I think you probably want to add the name to each line you print, such as:
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 827
Quoted 4 lines
mm/memcontrol.c +4
-0+printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));const char *name = memcg->css.cgroup->dentry->d_name.name; printk(KERN_INFO "Cgroup %s memory: usage %llu, limit %llu" " failcount %llu\n", name, ...);mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 832
Quoted 5 lines
mm/memcontrol.c +5
-0+printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT ));and
Quoted 5 lines
printk(KERN_INFO "Cgroup %s memory+swap: usage %llu, limit %llu " "failcnt %llu\n", name, ...);Quoted 1 line
mm/memcontrol.c +1
-0+}
Thanks for the review, I'll incorporate as much of it as possible in the next version.
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 45 lines · David Rientjes
Quoted 4 lines · Balbir Singh
David, I'd agree, but since we are under
printk_ratelimit()and this is a not-so-common path, does the log level matter much? If it does, I don't mind usingKERN_INFO.It matters for parsing dmesg output; the only
KERN_WARNINGmessage from the oom killer is normally the header. There's a couple extra ones for error conditions (that could certainly be changed toKERN_ERR), but only in very rare circumstances.As defined by
include/linux/kernel.h:#define KERN_WARNING "<4>" /* warning conditions */ ... #define KERN_INFO "<6>" /* informational */The meminfo you are printing falls under the "informational" category, no?
While you're there, it might also be helpful to make another change that would also help in parsing the output:
Quoted 6 lines
mm/memcontrol.c +0
-0@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 823
Quoted 10 lines
mm/memcontrol.c +8
-0return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name);This should be "cgroup's", but I don't think you want to print this on a line by itself since the only system-wide synchronization here is a read-lock on
tasklist_lockand there could be two separate memcg's that are oom.
Quoted 5 lines
So it's quite possible, though unlikely, that two seperate oom events would have these messages merged together in the ring buffer, which would make parsing impossible.
I think you probably want to add the name to each line you print, such as:
See below
Quoted 19 lines
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 827
Quoted 5 lines
mm/memcontrol.c +4
-0+printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));const char *name = memcg->css.cgroup->dentry->d_name.name; printk(KERN_INFO "Cgroup %s memory: usage %llu, limit %llu" " failcount %llu\n", name, ...);mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 832
Quoted 5 lines
mm/memcontrol.c +5
-0+printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT ));and
Quoted 5 lines
printk(KERN_INFO "Cgroup %s memory+swap: usage %llu, limit %llu " "failcnt %llu\n", name, ...);Quoted 1 line
mm/memcontrol.c +1
-0+}
FYI, we have OOM serialization via the memcg_tasklist mutex in the memory controller.
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
David Rientjes
reviewerQuoted 49 lines · Balbir Singh
Quoted 22 lines
Quoted 6 lines
mm/memcontrol.c +0
-0@@ -813,6 +813,25 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 823
Quoted 10 lines
mm/memcontrol.c +8
-0return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +if (!memcg) +return ; + +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name);This should be "cgroup's", but I don't think you want to print this on a line by itself since the only system-wide synchronization here is a read-lock on
tasklist_lockand there could be two separate memcg's that are oom.Quoted 5 lines
So it's quite possible, though unlikely, that two seperate oom events would have these messages merged together in the ring buffer, which would make parsing impossible.
I think you probably want to add the name to each line you print, such as:
See below
Quoted 19 lines
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 827
Quoted 5 lines
mm/memcontrol.c +4
-0+printk (KERN_WARNING "Cgroup memory: usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT ));const char *name = memcg->css.cgroup->dentry->d_name.name; printk(KERN_INFO "Cgroup %s memory: usage %llu, limit %llu" " failcount %llu\n", name, ...);mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 832
Quoted 5 lines
mm/memcontrol.c +5
-0+printk (KERN_WARNING "Cgroup memory+swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT ));and
Quoted 9 lines
Quoted 5 lines
printk(KERN_INFO "Cgroup %s memory+swap: usage %llu, limit %llu " "failcnt %llu\n", name, ...);Quoted 1 line
mm/memcontrol.c +1
-0+}FYI, we have OOM serialization via the
memcg_tasklistmutex in the memory controller.
I think it would be easier to parse in userspace if you provided the cgroup name on the same lines as the usage, limit, and failcnt values instead of storing that from the header line, but do whatever you want.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Johannes Weiner
maintainerQuoted 77 lines · Balbir Singh
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
From: Balbir Singh <[email protected]>
Description: Add RSS and swap to OOM output from memcg
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
Signed-off-by Balbir Singh <[email protected]>---
include/linux/memcontrol.h | 5 +++++ mm/memcontrol.c | 15 +++++++++++++++ mm/oom_kill.c | 1 + 3 files changed, 21 insertions(+), 0 deletions(-)include/linux/memcontrol.h +5
-0@@ -104,6 +104,7 @@ struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat(struct mem_cgroup *memcg, struct zone *zone);struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat_from_page (struct page *page); +extern void mem_cgroup_print_mem_info (struct mem_cgroup *memcg);#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP extern int do_swap_account;@@ -270,6 +271,10 @@ mem_cgroup_get_reclaim_stat_from_page(struct page *page)return NULL ; } +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +} +#endif /* CONFIG_CGROUP_MEM_CONT */ #endif /* _LINUX_MEMCONTROL_H */ mm/memcontrol.c +15
-0@@ -813,6 +813,21 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked. mm/oom_kill.c +0
-0
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 4 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);
mem is only !NULL when we come from mem_cgroup_out_of_memory(). This crashes otherwise in mem_cgroup_print_mem_info(), no?
Hannes
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 77 lines · Johannes Weiner
Quoted 76 lines · Balbir Singh
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
From: Balbir Singh <[email protected]>
Description: Add RSS and swap to OOM output from memcg
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
Signed-off-by Balbir Singh <[email protected]>---
include/linux/memcontrol.h | 5 +++++ mm/memcontrol.c | 15 +++++++++++++++ mm/oom_kill.c | 1 + 3 files changed, 21 insertions(+), 0 deletions(-)include/linux/memcontrol.h +5
-0@@ -104,6 +104,7 @@ struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat(struct mem_cgroup *memcg, struct zone *zone);struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat_from_page (struct page *page); +extern void mem_cgroup_print_mem_info (struct mem_cgroup *memcg);#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP extern int do_swap_account;@@ -270,6 +271,10 @@ mem_cgroup_get_reclaim_stat_from_page(struct page *page)return NULL ; } +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +} +#endif /* CONFIG_CGROUP_MEM_CONT */ #endif /* _LINUX_MEMCONTROL_H */ mm/memcontrol.c +15
-0@@ -813,6 +813,21 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked. mm/oom_kill.c +0
-0
Quoted 9 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 5 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);mem is only !NULL when we come from
mem_cgroup_out_of_memory(). This crashes otherwise inmem_cgroup_print_mem_info(), no?
I think you're right.
IMHO, "mem_cgroup_print_mem_info(current)" would be better here, and call mem_cgroup_from_task at mem_cgroup_print_mem_info.
Thanks,
Daisuke Nishimura.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
mm/oom_kill.c +0
-0Quoted 9 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 5 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);mem is only !NULL when we come from
mem_cgroup_out_of_memory(). This crashes otherwise inmem_cgroup_print_mem_info(), no?
Quoted 5 lines
I think you're right.
IMHO, "
mem_cgroup_print_mem_info(current)" would be better here, and callmem_cgroup_from_taskatmem_cgroup_print_mem_info.
Reading other messages on this thread, mem_cgroup_print_mem_info should be called only when oom_kill_process is called from mem_cgroup_out_of_memory, so checking "if (!mem)" would be enough.
Thanks,
Daisuke Nishimura.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
David Rientjes
reviewerQuoted 13 lines · Daisuke Nishimura
Quoted 13 lines
Quoted 13 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 9 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);mem is only !NULL when we come from
mem_cgroup_out_of_memory(). This crashes otherwise inmem_cgroup_print_mem_info(), no?
Quoted 9 lines
Quoted 5 lines
I think you're right.
IMHO, "
mem_cgroup_print_mem_info(current)" would be better here, and callmem_cgroup_from_taskatmem_cgroup_print_mem_info.Reading other messages on this thread,
mem_cgroup_print_mem_infoshould be called only whenoom_kill_processis called frommem_cgroup_out_of_memory, so checking "if (!mem)" would be enough.
You're right, but it's understandable why there would be confusion since it's very poorly documented.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 7 lines · Balbir Singh
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
Description: Add RSS and swap to OOM output from memcg
From: Balbir Singh <[email protected]>
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
---
include/linux/memcontrol.h | 5 +++++ mm/memcontrol.c | 16 ++++++++++++++++ mm/oom_kill.c | 1 + 3 files changed, 22 insertions(+), 0 deletions(-)
include/linux/memcontrol.h +5 -0
@@ -104,6 +104,7 @@ struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat(struct mem_cgroup *memcg, struct zone *zone);struct zone_reclaim_stat *mem_cgroup_get_reclaim_stat_from_page (struct page *page); +extern void mem_cgroup_print_mem_info (struct mem_cgroup *memcg);#ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP extern int do_swap_account;
@@ -270,6 +271,10 @@ mem_cgroup_get_reclaim_stat_from_page(struct page *page)return NULL ; } +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +} +#endif /* CONFIG_CGROUP_MEM_CONT */ #endif /* _LINUX_MEMCONTROL_H */
mm/memcontrol.c +16 -0
@@ -813,6 +813,22 @@ bool mem_cgroup_oom_called(struct task_struct *task)rcu_read_unlock ();return ret; } + +void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); +printk (KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" +" failcnt %llu\n" ,res_counter_read_u64 (&memcg->res,RES_USAGE ), +res_counter_read_u64 (&memcg->res,RES_LIMIT ), +res_counter_read_u64 (&memcg->res,RES_FAILCNT )); +printk (KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " +"failcnt %llu\n" , +res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), +res_counter_read_u64 (&memcg->memsw,RES_FAILCNT )); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked.
mm/oom_kill.c +1 -0
@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);task_unlock (current);dump_stack ();show_mem ();
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 11 lines · On Mon, 2 Feb 2009 19:38:49 +0530 Balbir Singh <[email protected]>…
Quoted 7 lines · Balbir Singh
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
Quoted 8 lines
Description: Add RSS and swap to OOM output from memcg
From: Balbir Singh <[email protected]>
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
please use "KB" not bytes in OOM killer information.
And the most important information is dropped..
Even if you show information, the most important information that "where I am and where we hit limit ?" is not coverred. Could you consider some way to show full-path ?
OOM-Killer:
Task in /memory/xxx/yyy/zzz is killed by
Limit of /memory/xxxx
RSS Limit : Usage: Failcnt....
RSS+SWAP Limit: ....
Thanks,
-Kame
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 30 lines · KAMEZAWA Hiroyuki
Quoted 11 lines · On Mon, 2 Feb 2009 19:38:49 +0530 Balbir Singh <[email protected]>…
Quoted 7 lines · Balbir Singh
Hi, All,
I found the following patch useful while debugging the memory controller. It adds additional information if memcg invoked the OOM.
Comments, Suggestions?
Quoted 8 lines
Description: Add RSS and swap to OOM output from memcg
From: Balbir Singh <[email protected]>
This patch displays memcg values like failcnt, usage and limit when an OOM occurs due to memcg.
please use "KB" not bytes in OOM killer information.
And the most important information is dropped..
Even if you show information, the most important information that "where I am and where we hit limit ?" is not coverred. Could you consider some way to show full-path ?
Quoted 6 lines
OOM-Killer:
Task in /memory/xxx/yyy/zzz is killed by
Limit of /memory/xxxx
RSS Limit : Usage: Failcnt....
RSS+SWAP Limit: ....
Sounds good to me, let me add this information.
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 822
Quoted 6 lines
mm/memcontrol.c +6
-0+void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); + printk(KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" + " failcnt %llu\n", res_counter_read_u64(&memcg->res, RES_USAGE),
", failcnt %llu\n" ?
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 826
Quoted 4 lines
mm/memcontrol.c +4
-0+res_counter_read_u64 (&memcg->res,RES_LIMIT ), + res_counter_read_u64(&memcg->res, RES_FAILCNT)); + printk(KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " + "failcnt %llu\n",
", failcnt %llu\n" ?
Quoted 13 lines
mm/memcontrol.c +5
-0+res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), + res_counter_read_u64(&memcg->memsw, RES_FAILCNT)); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked. mm/oom_kill.c +0
-0
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 4 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);
I think this can be put outside the task lock. The lock is used to call task_cs() safely in cpuset_print_task_mems_allowed().
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 398
Quoted 4 lines
mm/oom_kill.c +0
-0task_unlock (current);dump_stack ();show_mem ();
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 28 lines · Li Zefan
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 822
Quoted 6 lines
mm/memcontrol.c +6
-0+void mem_cgroup_print_mem_info (struct mem_cgroup *memcg) +{ +printk (KERN_WARNING "Memory cgroups's name %s\n" , + memcg->css.cgroup->dentry->d_name.name); + printk(KERN_WARNING "Memory cgroup RSS : usage %llu, limit %llu" + " failcnt %llu\n", res_counter_read_u64(&memcg->res, RES_USAGE),", failcnt %llu\n" ?
mm/memcontrol.c bool mem_cgroup_oom_called(struct task_struct *task) · line 826
Quoted 4 lines
mm/memcontrol.c +4
-0+res_counter_read_u64 (&memcg->res,RES_LIMIT ), + res_counter_read_u64(&memcg->res, RES_FAILCNT)); + printk(KERN_WARNING "Memory cgroup swap: usage %llu, limit %llu " + "failcnt %llu\n",", failcnt %llu\n" ?
Quoted 12 lines
mm/memcontrol.c +5
-0+res_counter_read_u64 (&memcg->memsw,RES_USAGE ), +res_counter_read_u64 (&memcg->memsw,RES_LIMIT ), + res_counter_read_u64(&memcg->memsw, RES_FAILCNT)); +} +/* * Unlike exported interface, "oom" parameter is added. if oom==true, * oom-killer can be invoked. mm/oom_kill.c +0
-0
Quoted 9 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 5 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().
Thanks, I'll work on that in the next version.
Quoted 5 lines
Quoted 4 lines
mm/oom_kill.c +0
-0task_unlock (current);dump_stack ();show_mem ();
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
David Rientjes
reviewerQuoted 14 lines · Balbir Singh
Quoted 4 lines
Quoted 4 lines
mm/oom_kill.c +0
-0Quoted 9 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 5 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().
Quoted 2 lines
Thanks, I'll work on that in the next version.
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If task_lock() isn't held, is the memcg->css.cgroup->dentry->d_name.name dereference always safe without rcu?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 16 lines · David Rientjes
Quoted 14 lines · Balbir Singh
Quoted 13 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 9 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().
Quoted 8 lines
Quoted 2 lines
Thanks, I'll work on that in the next version.
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If
task_lock()isn't held, is thememcg->css.cgroup->dentry->d_name.namedereference always safe without rcu?
oom_kill_process is called with tasklist_lock held (read-mode). That should suffice, no? The memcg cannot go away since it has other groups or tasks associated with it.
Signature · 1 line
Balbir
David Rientjes
reviewerQuoted 23 lines · Balbir Singh
Quoted 14 lines
Quoted 14 lines
Quoted 13 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 9 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().Quoted 8 lines
Quoted 2 lines
Thanks, I'll work on that in the next version.
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If
task_lock()isn't held, is thememcg->css.cgroup->dentry->d_name.namedereference always safe without rcu?
Quoted 4 lines
oom_kill_processis called withtasklist_lockheld (read-mode). That should suffice, no? The memcg cannot go away since it has other groups or tasks associated with it.
I don't see how this prevents a task from being reattached to a different cgroup and then a rmdir on memcg->css.cgroup would destroy the dentry without cgroup_mutex or dereferencing via rcu.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 25 lines · David Rientjes
Quoted 23 lines · Balbir Singh
Quoted 22 lines
Quoted 14 lines
Quoted 4 lines
Quoted 4 lines
mm/oom_kill.c +0
-0Quoted 9 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 5 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().Quoted 2 lines
Thanks, I'll work on that in the next version.
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If
task_lock()isn't held, is thememcg->css.cgroup->dentry->d_name.namedereference always safe without rcu?
Quoted 8 lines
Quoted 4 lines
oom_kill_processis called withtasklist_lockheld (read-mode). That should suffice, no? The memcg cannot go away since it has other groups or tasks associated with it.I don't see how this prevents a task from being reattached to a different cgroup and then a rmdir on
memcg->css.cgroupwould destroy the dentry withoutcgroup_mutexor dereferencing via rcu.
That scenario is not possible today from the memory controller perspective.
We hold memcg_tasklist during task movement and during OOM, task migration is held till OOM completes.
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 14 lines · David Rientjes
Quoted 12 lines · Balbir Singh
Quoted 12 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 9 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().
Quoted 8 lines
Quoted 2 lines
Thanks, I'll work on that in the next version.
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If
task_lock()isn't held, is thememcg->css.cgroup->dentry->d_name.namedereference always safe without rcu?
The cgroup won't disappear, since mem_cgroup_out_of_memory() is called with memcg's css refcnt increased. :)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>
Quoted 18 lines · Li Zefan
Quoted 17 lines · David Rientjes
Quoted 14 lines · Balbir Singh
Quoted 12 lines
mm/oom_kill.c static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, · line 395
Quoted 9 lines
mm/oom_kill.c +1
-0@@ -392,6 +392,7 @@ static int oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order, current->comm, gfp_mask, order, current->oomkilladj);task_lock (current);cpuset_print_task_mems_allowed (current); +mem_cgroup_print_mem_info (mem);I think this can be put outside the task lock. The lock is used to call
task_cs()safely incpuset_print_task_mems_allowed().Thanks, I'll work on that in the next version.
Quoted 9 lines
Quoted 5 lines
I was also wondering about this and assumed that it was necessary to prevent the cgroup from disappearing during the oom. If
task_lock()isn't held, is thememcg->css.cgroup->dentry->d_name.namedereference always safe without rcu?The cgroup won't disappear, since
mem_cgroup_out_of_memory()is called with memcg's css refcnt increased. :)
And this as well, yes!
Signature · 7 lines
Balbir -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>