diff options
| author | Joonsoo Kim <iamjoonsoo.kim@lge.com> | 2015-02-12 00:27:06 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-02-12 02:06:04 +0100 |
| commit | 837d026d560c5ef26abeca0441713d82e4e82cad (patch) | |
| tree | 074e7941df8d83fc7fdb0680883989c84c3d654c /mm/mempolicy.c | |
| parent | mm/compaction: print current range where compaction work (diff) | |
| download | linux-837d026d560c5ef26abeca0441713d82e4e82cad.tar.xz linux-837d026d560c5ef26abeca0441713d82e4e82cad.zip | |
mm/compaction: more trace to understand when/why compaction start/finish
It is not well analyzed that when/why compaction start/finish or not.
With these new tracepoints, we can know much more about start/finish
reason of compaction. I can find following bug with these tracepoint.
http://www.spinics.net/lists/linux-mm/msg81582.html
Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: Mel Gorman <mgorman@suse.de>
Cc: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/mempolicy.c')
0 files changed, 0 insertions, 0 deletions