Prev: [PATCH 1/3] KVM: MMU: remove unnecessary remote tlb flush
Next: [PATCH 2/3] KVM: MMU: using wrapper function to flush local tlb
From: KOSAKI Motohiro on 8 Jun 2010 08:10 Now, all of oom developers usually are using sysctl_oom_dump_tasks. Redundunt useless debug print can be removed. Signed-off-by: KOSAKI Motohiro <kosaki.motohiro(a)jp.fujitsu.com> --- mm/oom_kill.c | 5 ----- 1 files changed, 0 insertions(+), 5 deletions(-) diff --git a/mm/oom_kill.c b/mm/oom_kill.c index 8376ad1..e7d3a5d 100644 --- a/mm/oom_kill.c +++ b/mm/oom_kill.c @@ -33,7 +33,6 @@ int sysctl_panic_on_oom; int sysctl_oom_kill_allocating_task; int sysctl_oom_dump_tasks = 1; static DEFINE_SPINLOCK(zone_scan_lock); -/* #define DEBUG */ /* * Is all threads of the target process nodes overlap ours? @@ -201,10 +200,6 @@ unsigned long oom_badness(struct task_struct *p, unsigned long uptime) points >>= -(oom_adj); } -#ifdef DEBUG - printk(KERN_DEBUG "OOMkill: task %d (%s) got %lu points\n", - p->pid, p->comm, points); -#endif return points; } -- 1.6.5.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |