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;
Message-Id: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
From:   Colin Walters <walters@verbum.org>
To:     Shawn Landden <slandden@gmail.com>
Cc:     linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
        linux-mm@kvack.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
References: <20171101053244.5218-1-slandden@gmail.com>
 <1509549397.2561228.1158168688.4CFA4326@webmail.messagingengine.com>
Date:   Wed, 01 Nov 2017 11:22:29 -0400
In-Reply-To: <1509549397.2561228.1158168688.4CFA4326@webmail.messagingengine.com>
Subject: Re: [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes process
 to death row (new syscall)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk


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?

From 1582877338770114892@xxx Wed Nov 01 15:17:44 +0000 2017
X-GM-THRID: 1582840593921048574
X-Gmail-Labels: Inbox,Category Forums