From: Michal Hocko <firstname.lastname@example.org> To: David Rientjes <email@example.com> Cc: Tetsuo Handa <firstname.lastname@example.org>, Johannes Weiner <email@example.com>, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, firstname.lastname@example.org, email@example.com, Andrew Morton <firstname.lastname@example.org>, Sergey Senozhatsky <email@example.com>, Petr Mladek <firstname.lastname@example.org>, Sergey Senozhatsky <email@example.com>, Steven Rostedt <firstname.lastname@example.org> Subject: Re: [PATCH] mm,oom: Use timeout based back off. Date: Tue, 23 Oct 2018 07:56:55 +0200 [thread overview] Message-ID: <20181023055655.GM18839@dhcp22.suse.cz> (raw) In-Reply-To: <alpine.DEB.email@example.com> On Mon 22-10-18 14:11:10, David Rientjes wrote: [...] > I've proposed patches that have been running for months in a production > environment that make the oom killer useful without serially killing many > processes unnecessarily. At this point, it is *much* easier to just fork > the oom killer logic rather than continue to invest time into fixing it in > Linux. That's unfortunate because I'm sure you realize how problematic > the current implementation is, how abusive it is, and have seen its > effects yourself. I admire your persistance in trying to fix the issues > surrounding the oom killer, but have come to the conclusion that forking > it is a much better use of time. These are some pretty strong words for a code that tends to work for most users out there. I do not remember any bug reports except for artificial stress tests or your quite unspecific claims about absolutely catastrophic impact which is not backed by any specific details. I have shown interest in addressing as many issues as possible but I absolutely detest getting back to the previous state with an indeterministic pile of heuristic which were lockup prone and basically unmaintainable. Going around with timeouts and potentially export them to userspace might sound attractive for the simplicity but this should be absolutely the last resort when a proper solution is too complex (from a code or maintainability POV). I do not believe we have reached that state yet. -- Michal Hocko SUSE Labs
next prev parent reply other threads:[~2018-10-23 5:57 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-10-20 10:57 Tetsuo Handa 2018-10-22 21:11 ` David Rientjes 2018-10-23 5:56 ` Michal Hocko [this message] 2018-10-24 22:54 ` Andrew Morton 2018-10-25 7:11 ` Michal Hocko
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20181023055655.GM18839@dhcp22.suse.cz \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] mm,oom: Use timeout based back off.' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.