From: Johannes Weiner <hannes@cmpxchg.org>
To: Hillf Danton <hdanton@sina.com>
Cc: linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
Shakeel Butt <shakeelb@google.com>,
Minchan Kim <minchan@kernel.org>, Mel Gorman <mgorman@suse.de>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Jan Kara <jack@suse.cz>
Subject: Re: [RFC v2] mm: add page preemption
Date: Mon, 28 Oct 2019 11:56:17 -0400 [thread overview]
Message-ID: <20191028155617.GA3156@cmpxchg.org> (raw)
In-Reply-To: <20191026112808.14268-1-hdanton@sina.com>
On Sat, Oct 26, 2019 at 07:28:08PM +0800, Hillf Danton wrote:
>
> The cpu preemption feature makes a task able to preempt other tasks
> of lower priorities for cpu. It has been around for a while.
>
> This work introduces task prio into page reclaiming in order to add
> the page preemption feature that makes a task able to preempt other
> tasks of lower priorities for page.
>
> No page will be reclaimed on behalf of tasks of lower priorities
... at which point they'll declare OOM and kill the high-pri task?
Please have a look at the cgroup2 memory.low control. This memory
prioritization problem has already been solved.
next prev parent reply other threads:[~2019-10-28 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20191026112808.14268-1-hdanton@sina.com>
2019-10-28 12:26 ` [RFC v2] mm: add page preemption Kirill A. Shutemov
2019-10-28 15:56 ` Johannes Weiner [this message]
2019-10-29 8:41 ` Michal Hocko
2019-10-29 15:27 ` Johannes Weiner
[not found] <20191029123058.19060-1-hdanton@sina.com>
2019-10-29 13:26 ` David Hildenbrand
2019-10-29 13:41 ` Michal Hocko
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=20191028155617.GA3156@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=hdanton@sina.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=shakeelb@google.com \
--cc=vdavydov.dev@gmail.com \
--cc=willy@infradead.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).