From owner-freebsd-hackers@freebsd.org  Fri Dec  8 10:17:03 2017
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id D0433EA0324
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Fri,  8 Dec 2017 10:17:03 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6502C6C1D7
 for <freebsd-hackers@freebsd.org>; Fri,  8 Dec 2017 10:17:03 +0000 (UTC)
 (envelope-from kostikbel@gmail.com)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id vB8AGwuv024784
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Fri, 8 Dec 2017 12:16:59 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua vB8AGwuv024784
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id vB8AGwBY024783;
 Fri, 8 Dec 2017 12:16:58 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Fri, 8 Dec 2017 12:16:58 +0200
From: Konstantin Belousov <kostikbel@gmail.com>
To: Johannes Lundberg <johalun0@gmail.com>
Cc: Larry McVoy <lm@mcvoy.com>, freebsd-hackers@freebsd.org
Subject: Re: OOM problem?
Message-ID: <20171208101658.GD2272@kib.kiev.ua>
References: <20171208011430.GA16016@mcvoy.com>
 <CAECmPwtcsHwiZpmx4+T_w3njEdUAjGZiRZKEX53m-QVJLSuY9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAECmPwtcsHwiZpmx4+T_w3njEdUAjGZiRZKEX53m-QVJLSuY9Q@mail.gmail.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Dec 2017 10:17:03 -0000

On Fri, Dec 08, 2017 at 08:18:21AM +0000, Johannes Lundberg wrote:
> Regarding potential oom overhaul. Personally I like the idea of an oom
> signal. The idea comes from iOS where applications get a callback when
> system memory is low and they're given a chance to free unused
> resources or resources that can easily be recreated, before getting
> killed completely.
The OOM signal is a topic which was discussed to death many times before.
The summary is that it does not work, because you need to provide pages
for userspace to be able to handle the signal.