I'm looking for comments on how to avoid the failure scenario where a correctly
configured system fails to boot after taking corrective action when a memory
module goes bad. Right now if there is a memory event that causes a system
reboot and the UEFI to remove the memory from the memory pool, it may result in
Linux not having enough memory to boot due to the huge page reserve.
The patch in its current state will reclaim hugepages if they are free
regardless of on boot or not - which may not be desirable, or maybe it is?
I've looked through how select_bad_process works and do not see a clean way to
hook in to this function when the victim is not a task.
I also could not find a good place to add the CONFIG_HUGETLB_PAGE_OOM.
Obviously that would need to go somewhere sane.
Liam R. Howlett (1):
mm/hugetlb mm/oom_kill: Add support for reclaiming hugepages on OOM
events.
include/linux/hugetlb.h | 1 +
mm/hugetlb.c | 35 +++++++++++++++++++++++++++++++++++
mm/oom_kill.c | 8 ++++++++
3 files changed, 44 insertions(+)
--
2.13.0.90.g1eb437020
--
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>
