From: Shawn Landden <slandden@gmail.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org, linux-api@vger.kernel.org
Subject: Re: [RFC v2] prctl: prctl(PR_SET_IDLE, PR_IDLE_MODE_KILLME), for stateless idle loops
Date: Sat, 18 Nov 2017 12:33:50 -0800 [thread overview]
Message-ID: <CA+49okpufRcRD=VfjWkEi_XSc+Uyn+291Npz-K2J34f5AjFxrA@mail.gmail.com> (raw)
In-Reply-To: <20171103090915.uuaqo56phdbt6gnf@dhcp22.suse.cz>
On Fri, Nov 3, 2017 at 2:09 AM, Michal Hocko <mhocko@kernel.org> wrote:
> On Thu 02-11-17 23:35:44, Shawn Landden wrote:
>> 16 bytes per process is kinda spendy, but I want to keep
>> lru behavior, which mem_score_adj does not allow. When a supervisor,
>> like Android's user input is keeping track this can be done in user-space.
>> It could be pulled out of task_struct if an cross-indexing additional
>> red-black tree is added to support pid-based lookup.
>
> This is still an abuse and the patch is wrong. We really do have an API
> to use I fail to see why you do not use it.
When I looked at wait_queue_head_t it was 20 bytes.
next prev parent reply other threads:[~2017-11-18 20:34 UTC|newest]
Thread overview: 23+ 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 14:04 ` Matthew Wilcox
2017-11-01 15:16 ` Colin Walters
2017-11-01 15:22 ` Colin Walters
2017-11-03 9:22 ` peter enderborg
[not found] ` <CA+49okox_Hvg-dGyjZc3u0qLz1S=LJjS4-WT6SxQ9qfPyp6BjQ@mail.gmail.com>
2017-11-01 19:37 ` Colin Walters
2017-11-02 15:24 ` Shawn Paul Landden
2017-11-01 22:10 ` Tetsuo Handa
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 9:09 ` Michal Hocko
2017-11-18 20:33 ` Shawn Landden [this message]
[not found] ` <CA+49okqZ8CME0EN1xS_cCTc5Q-fGRreg0makhzNNuRpGs3mjfw@mail.gmail.com>
2017-11-19 4:19 ` Matthew Wilcox
2017-11-20 8:35 ` Michal Hocko
2017-11-21 4:48 ` Shawn Landden
2017-11-21 7:05 ` Michal Hocko
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:56 ` Shawn Landden
2017-11-21 5:16 ` [RFC v4] " Shawn Landden
2017-11-21 5:26 ` Shawn Landden
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
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='CA+49okpufRcRD=VfjWkEi_XSc+Uyn+291Npz-K2J34f5AjFxrA@mail.gmail.com' \
--to=slandden@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).