Re: Some interesting news about Linux 3.12 OOM

From: Greg Stark <stark(at)mit(dot)edu>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Some interesting news about Linux 3.12 OOM
Date: 2013-09-25 15:00:55
Message-ID: CAM-w4HN=Z-hBEz8GcvQ1F-MWLnMCyRGMSrJBbNGGO4PsQo9Hew@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 25, 2013 at 12:15 AM, Daniel Farina <daniel(at)heroku(dot)com> wrote:

> Enable the memcg OOM killer only for user faults, where it's really the
> only option available.
>

Is this really a big deal? I would expect most faults to be user faults.

It's certainly a big deal that we need to ensure we can handle ENOMEM from
syscalls and library functions we weren't expecting to return it. But I
don't expect it to actually reduce the OOM killing sprees by much.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Steve Singer 2013-09-25 15:01:44 Re: logical changeset generation v6
Previous Message Heikki Linnakangas 2013-09-25 14:52:47 Re: Freezing without write I/O