From: peter enderborg <peter.enderborg@sonymobile.com>
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>
Subject: Re: [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes process to death row (new syscall)
Date: Fri, 3 Nov 2017 10:22:49 +0100 [thread overview]
Message-ID: <2cc07a12-9cf4-429b-11d3-269c486879e3@sonymobile.com> (raw)
In-Reply-To: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
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.
WARNING: multiple messages have this Message-ID (diff)
From: peter enderborg <peter.enderborg@sonymobile.com>
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>
Subject: Re: [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes process to death row (new syscall)
Date: Fri, 3 Nov 2017 10:22:49 +0100 [thread overview]
Message-ID: <2cc07a12-9cf4-429b-11d3-269c486879e3@sonymobile.com> (raw)
In-Reply-To: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: peter enderborg <peter.enderborg@sonymobile.com>
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
Subject: Re: [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes process to death row (new syscall)
Date: Fri, 3 Nov 2017 10:22:49 +0100 [thread overview]
Message-ID: <2cc07a12-9cf4-429b-11d3-269c486879e3@sonymobile.com> (raw)
In-Reply-To: <1509549749.2563336.1158179384.52E1E4B4@webmail.messagingengine.com>
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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-11-03 9:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-01 5:32 [RFC] EPOLL_KILLME: New flag to epoll_wait() that subscribes process to death row (new syscall) Shawn Landden
2017-11-01 5:32 ` Shawn Landden
2017-11-01 5:32 ` Shawn Landden
2017-11-01 14:04 ` Matthew Wilcox
2017-11-01 14:04 ` Matthew Wilcox
2017-11-01 15:16 ` Colin Walters
2017-11-01 15:16 ` Colin Walters
2017-11-01 15:22 ` Colin Walters
2017-11-01 15:22 ` Colin Walters
2017-11-03 9:22 ` peter enderborg [this message]
2017-11-03 9:22 ` peter enderborg
2017-11-03 9:22 ` peter enderborg
2017-11-01 19:02 ` Shawn Landden
2017-11-01 19:37 ` Colin Walters
2017-11-01 19:37 ` Colin Walters
2017-11-01 19:43 ` Shawn Landden
2017-11-01 20:54 ` Shawn Landden
2017-11-02 15:24 ` Shawn Paul Landden
2017-11-02 15:24 ` Shawn Paul Landden
2017-11-01 19:05 ` Shawn Landden
2017-11-01 22:10 ` Tetsuo Handa
2017-11-01 22:10 ` Tetsuo Handa
2017-11-02 7:36 ` Shawn Landden
2017-11-02 15:45 ` Michal Hocko
2017-11-02 15:45 ` Michal Hocko
2017-11-03 6:35 ` [RFC v2] prctl: prctl(PR_SET_IDLE, PR_IDLE_MODE_KILLME), for stateless idle loops Shawn Landden
2017-11-03 6:35 ` Shawn Landden
2017-11-03 6:35 ` Shawn Landden
2017-11-03 9:09 ` Michal Hocko
2017-11-03 9:09 ` Michal Hocko
2017-11-18 4:45 ` Shawn Landden
2017-11-19 4:19 ` Matthew Wilcox
2017-11-19 4:19 ` Matthew Wilcox
2017-11-19 4:19 ` Matthew Wilcox
2017-11-20 8:35 ` Michal Hocko
2017-11-20 8:35 ` Michal Hocko
2017-11-21 4:48 ` Shawn Landden
2017-11-21 4:48 ` Shawn Landden
2017-11-21 7:05 ` Michal Hocko
2017-11-21 7:05 ` Michal Hocko
2017-11-18 20:33 ` Shawn Landden
2017-11-18 20:33 ` Shawn Landden
2017-11-15 21:11 ` Pavel Machek
2017-11-21 4:49 ` [RFC v3] It is common for services to be stateless around their main event loop. If a process sets PR_SET_IDLE to PR_IDLE_MODE_KILLME then it signals to the kernel that epoll_wait() and friends may not complete, and the kernel may send SIGKILL if resources get tight Shawn Landden
2017-11-21 4:49 ` Shawn Landden
2017-11-21 4:49 ` Shawn Landden
2017-11-21 4:56 ` Shawn Landden
2017-11-21 4:56 ` Shawn Landden
2017-11-21 5:16 ` [RFC v4] " Shawn Landden
2017-11-21 5:16 ` Shawn Landden
2017-11-21 5:16 ` Shawn Landden
2017-11-21 5:26 ` Shawn Landden
2017-11-21 5:26 ` Shawn Landden
2017-11-21 9:14 ` Thomas Gleixner
2017-11-21 9:14 ` Thomas Gleixner
2017-11-22 10:29 ` [RFC v2] prctl: prctl(PR_SET_IDLE, PR_IDLE_MODE_KILLME), for stateless idle loops peter enderborg
2017-11-22 10:29 ` peter enderborg
2017-11-22 10:29 ` peter enderborg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cc07a12-9cf4-429b-11d3-269c486879e3@sonymobile.com \
--to=peter.enderborg@sonymobile.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=slandden@gmail.com \
--cc=walters@verbum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.