On (10/18/18 09:56), Michal Hocko wrote: > On Thu 18-10-18 15:10:18, Sergey Senozhatsky wrote: > [...] > > and let's hear from MM people what they can suggest. > > > > Michal, Andrew, Johannes, any thoughts? > > I have already stated my position. Let's not reinvent the wheel and use > the standard printk throttling. If there are cases where oom reports > cause more harm than good I am open to add a knob to allow disabling it > altogether (it can be even fine grained one to control whether to dump > show_mem, task_list etc.). A knob might do. As well as /proc/sys/kernel/printk tweaks, probably. One can even add echo "a b c d" > /proc/sys/kernel/printk to .bashrc and adjust printk console levels on login and rollback to old values in .bash_logout May be. > But please let's stop this dubious one-off approaches. OK. Well, I'm not proposing anything actually. I didn't even realize until recently that Tetsuo was talking about "user interaction" problem; I thought that his problem was stalled RCU. -ss
