Prev: [tip:tracing/core] tracing: Remove side effect from module tracepoints that caused a GPF
Next: [tip:x86/urgent] x86: Increase CONFIG_NODES_SHIFT max to 10
From: David Rientjes on 2 Apr 2010 15:10
On Fri, 2 Apr 2010, Oleg Nesterov wrote:
> It doesn't make sense to call thread_group_cputime() under task_lock(),
> we can drop this lock right after we read get_mm_rss() and save the
> value in the local variable.
> Note: probably it makes more sense to use sum_exec_runtime instead
> of utime + stime, it is much more precise. A task can eat a lot of
> CPU time, but its Xtime can be zero.
> Signed-off-by: Oleg Nesterov <oleg(a)redhat.com>
Acked-by: David Rientjes <rientjes(a)google.com>
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/