summaryrefslogtreecommitdiffstats
path: root/Documentation/mmc/mmc-async-req.txt
diff options
context:
space:
mode:
authorDavid Rientjes <rientjes@google.com>2012-03-21 16:34:10 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2012-03-21 17:54:59 -0700
commite845e199362cc5712ba0e7eedc14eed70e144258 (patch)
tree3968125d82e512c3aee44ed96694fdd58b863506 /Documentation/mmc/mmc-async-req.txt
parentc7cfa37b7324a190fc36ff116d79d0f899e8d273 (diff)
downloadop-kernel-dev-e845e199362cc5712ba0e7eedc14eed70e144258.zip
op-kernel-dev-e845e199362cc5712ba0e7eedc14eed70e144258.tar.gz
mm, memcg: pass charge order to oom killer
The oom killer typically displays the allocation order at the time of oom as a part of its diangostic messages (for global, cpuset, and mempolicy ooms). The memory controller may also pass the charge order to the oom killer so it can emit the same information. This is useful in determining how large the memory allocation is that triggered the oom killer. Signed-off-by: David Rientjes <rientjes@google.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@suse.cz> Cc: Balbir Singh <bsingharora@gmail.com> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'Documentation/mmc/mmc-async-req.txt')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud