Re: [PATCH 3/5] mm: Remember ongoing memory allocation status.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun 23-11-14 13:51:31, Tetsuo Handa wrote:
> >From 0c6d4e0ac9fc5964fdd09849c99e4f6497b7a37e Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
> Date: Sun, 23 Nov 2014 13:40:20 +0900
> Subject: [PATCH 3/5] mm: Remember ongoing memory allocation status.
> 
> When a stall by memory allocation problem occurs, printing how long
> a thread was blocked for memory allocation will be useful.

Why tracepoints are not suitable for this debugging?

> This patch allows remembering how many jiffies was spent for ongoing
> __alloc_pages_nodemask() and reading it by printing backtrace and by
> analyzing vmcore.

__alloc_pages_nodemask is a hotpath of the allocation and it is not
really acceptable to add debugging stuff there which will have only very
limited usage.

[...]
-- 
Michal Hocko
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxx.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]