From: Tim Murray <timmurray@google.com>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Michal Hocko <mhocko@kernel.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
cgroups@vger.kernel.org, Linux-MM <linux-mm@kvack.org>,
Suren Baghdasaryan <surenb@google.com>,
Patrik Torstensson <totte@google.com>,
Android Kernel Team <kernel-team@android.com>
Subject: Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup
Date: Thu, 30 Mar 2017 14:54:28 -0700 [thread overview]
Message-ID: <CAEe=Sxmj6wHN9HzAix9F4HDhk9ojYaMrStE1b1MxB0VvMzd=Ug@mail.gmail.com> (raw)
In-Reply-To: <CAEe=SxmpXD=f9N_i+xe6gFUKKUefJYvBd8dSwxSM+7rbBBTniw@mail.gmail.com>
On Thu, Mar 30, 2017 at 12:40 PM, Tim Murray <timmurray@google.com> wrote:
> The current critical vmpressure event
> hasn't been that successful in avoiding oom-killer (on 3.18, at
> least)--I've been able to get oom-killer to trigger without a
> vmpressure event.
Looked at this some more, and this is almost certainly because
vmpressure relies on workqueues. Scheduling delay from CFS workqueues
would explain vmpressure latency that results in oom-killer running
long before the critical vmpressure notification is received in
userspace, even if userspace is running as FIFO. We regularly see
10ms+ latency on workqueues, even when an Android device isn't heavily
loaded.
--
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-03-30 21:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 23:16 Tim Murray
2017-03-17 23:16 ` [RFC 1/1] mm, memcg: add prioritized reclaim Tim Murray
2017-03-20 14:41 ` vinayak menon
2017-03-20 5:59 ` [RFC 0/1] add support for reclaiming priorities per mem cgroup Minchan Kim
2017-03-20 13:58 ` Vinayak Menon
2017-03-20 15:23 ` Johannes Weiner
2017-03-22 12:13 ` Vinayak Menon
2017-03-21 17:18 ` Tim Murray
2017-03-22 4:41 ` Minchan Kim
2017-03-22 5:20 ` Minchan Kim
2017-03-20 6:56 ` peter enderborg
2017-03-20 8:18 ` Kyungmin Park
2017-03-30 5:59 ` Minchan Kim
2017-03-30 7:10 ` Tim Murray
2017-03-30 15:51 ` Johannes Weiner
2017-03-30 16:48 ` Shakeel Butt
2017-04-13 16:03 ` Johannes Weiner
2017-03-30 19:40 ` Tim Murray
2017-03-30 21:54 ` Tim Murray [this message]
2017-04-13 4:30 ` Minchan Kim
2017-04-13 16:01 ` Johannes Weiner
2017-04-17 4:26 ` Minchan Kim
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='CAEe=Sxmj6wHN9HzAix9F4HDhk9ojYaMrStE1b1MxB0VvMzd=Ug@mail.gmail.com' \
--to=timmurray@google.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=surenb@google.com \
--cc=totte@google.com \
--cc=vdavydov.dev@gmail.com \
/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