Dmitry Monakhov wrote: > Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx> writes: > > > 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" > This still may result in hundreds of messages per second. Then, it means that your system is invoking the OOM killer one hundred times per second (every 10 milliseconds). I think that such system is far from properly configured. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
