Re: /proc/self/oom_adj is deprecated in newer Linux kernels

From: Jonathan Corbet <corbet(at)lwn(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Christoph Berg <cb(at)df7cb(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PGSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: /proc/self/oom_adj is deprecated in newer Linux kernels
Date: 2014-07-02 13:08:10
Message-ID: 20140702090810.73c5572d@lwn.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 1 Jul 2014 15:57:25 -0400
Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> Of course, we have no guarantee that the Linux kernel guys won't
> change this again. Apparently "we don't break userspace" is a
> somewhat selectively-enforced principle.

It's selectively enforced in that kernel developers don't (and can't)
scan the world for software that might break. OTOH, if somebody were
to respond to a proposed change by saying "this breaks PostgreSQL," I
would be amazed if the change were to be merged in that form.

In other words, it's important to scream. There were concerns during
the last round of messing with the OOM logic, but nobody pointed to
something that actually broke.

I predict that somebody will certainly try to rewrite the OOM code
again in the future. The nature of that code is such that it is never
going to work as well as people would like. But if application
developers make it clear that they are dependent on the current
interface working, kernel developers will be constrained to keep it
working.

jon

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2014-07-02 13:17:29 Re: better atomics - v0.5
Previous Message Andres Freund 2014-07-02 13:06:10 Re: better atomics - v0.5