On (12/19/16 20:25), Tetsuo Handa wrote: [..] > So, I'd like to check whether async printk() can prevent the system from reaching > the threshold. Though, I guess async printk() won't help for preemption outside > printk() (i.e. CONFIG_PREEMPT=y and/or longer sleep by schedule_timeout_killable(1) > after returning from oom_kill_process()). > > Sergey, will you share your async printk() patches? Hello, I don't have (yet) a re-based version, since printk has changed a lot once again during this merge window. the work is in progress now. the latest publicly available version is against the linux-next 20161202 https://gitlab.com/senozhatsky/linux-next-ss/commits/printk-safe-deferred I'll finish re-basing the patch set tomorrow. -ss -- 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>