From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754849AbdKAPWd (ORCPT ); Wed, 1 Nov 2017 11:22:33 -0400 Received: from out4-smtp.messagingengine.com ([66.111.4.28]:46623 "EHLO out4-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753815AbdKAPWa (ORCPT ); Wed, 1 Nov 2017 11:22:30 -0400 X-ME-Sender: Message-Id: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com> From: Colin Walters To: Shawn Landden 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" X-Mailer: MessagingEngine.com Webmail Interface - ajax-66b6e65c 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 List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?