Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes
 process to death row (new syscall)
To:     Colin Walters <walters@verbum.org>,
        Shawn Landden <slandden@gmail.com>
CC:     <linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
        <linux-mm@kvack.org>
References: <20171101053244.5218-1-slandden@gmail.com>
 <1509549397.2561228.1158168688.4CFA4326@webmail.messagingengine.com>
 <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
From:   peter enderborg <peter.enderborg@sonymobile.com>
Message-ID: <2cc07a12-9cf4-429b-11d3-269c486879e3@sonymobile.com>
Date:   Fri, 3 Nov 2017 10:22:49 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 11/01/2017 04:22 PM, Colin Walters wrote:
>
> On Wed, Nov 1, 2017, at 11:16 AM, Colin Walters wrote:
>> as the maintainer of glib2 which is used by a *lot* of things; I'm not
> (I meant to say "a" maintainer)
>
> Also, while I'm not an expert in Android, I think the "what to kill" logic
> there lives in userspace, right?   So it feels like we should expose this
> state in e.g. /proc and allow userspace daemons (e.g. systemd, kubelet) to perform
> idle collection too, even if the system isn't actually low on resources
> from the kernel's perspective.
>
> And doing that requires some sort of kill(pid, SIGKILL_IF_IDLE) or so?
>
You are right, in android it is the activity manager that performs this tasks. And if services
dies without talking to the activity manager the service is restarted, unless it is
on highest oom score. A other problem is that a lot communication in android is binder not epoll.

And a signal that can not be caught not that good. But a "warn" signal of the userspace choice in
something in a context similar to ulimit. SIGXFSZ/SIGXCPU that you can pickup and notify activity manager might work.

However, in android this is already solved with OnTrimMemory that is message sent from activitymanager to
application, services etc when system need memory back.


From 1582969733260573047@xxx Thu Nov 02 15:46:18 +0000 2017
X-GM-THRID: 1582840593921048574
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread