On 2017/11/08 18:18, Dmitry Monakhov wrote: > Our systems becomes bigger and bigger, but OOM still happens. > This becomes serious problem for systems where OOM happens > frequently(containers, VM) because each OOM generate pressure > on dmesg log infrastructure. Let's allow system administrator > ability to tune OOM dump behaviour Majority of OOM killer related messages are from dump_header(). Thus, allow tuning __ratelimit(&oom_rs) might make sense. But other lines "%s: Kill process %d (%s) score %u or sacrifice child\n" "Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n" "oom_reaper: reaped process %d (%s), now anon-rss:%lukB, file-rss:%lukB, shmem-rss:%lukB\n" should not cause problems, for it is easy to exclude such lines from your dmesg log infrastructure using fgrep match. -- 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>
