On Mon, Sep 17, 2018 at 04:08:46PM -0700, Roman Gushchin wrote: > The memcg OOM killer is never invoked due to a failed high-order > allocation, however the MEMCG_OOM event can be raised. > > As shown below, it can happen under conditions, which are very > far from a real OOM: e.g. there is plenty of clean pagecache > and low memory pressure. > > There is no sense in raising an OOM event in such a case, > as it might confuse a user and lead to wrong and excessive actions. > > Let's look at the charging path in try_caharge(). If the memory usage > is about memory.max, which is absolutely natural for most memory cgroups, > we try to reclaim some pages. Even if we were able to reclaim > enough memory for the allocation, the following check can fail due to > a race with another concurrent allocation: > > if (mem_cgroup_margin(mem_over_limit) >= nr_pages) > goto retry; > > For regular pages the following condition will save us from triggering > the OOM: > > if (nr_reclaimed && nr_pages <= (1 << PAGE_ALLOC_COSTLY_ORDER)) > goto retry; > > But for high-order allocation this condition will intentionally fail. > The reason behind is that we'll likely fall to regular pages anyway, > so it's ok and even preferred to return ENOMEM. > > In this case the idea of raising MEMCG_OOM looks dubious. > > Fix this by moving MEMCG_OOM raising to mem_cgroup_oom() after > allocation order check, so that the event won't be raised for high > order allocations. This change doesn't affect regular pages allocation > and charging. > > Signed-off-by: Roman Gushchin <g...@fb.com> > Acked-by: David Rientjes <rient...@google.com> > Cc: Johannes Weiner <han...@cmpxchg.org> > Cc: Michal Hocko <mho...@kernel.org> > Cc: Vladimir Davydov <vdavydov....@gmail.com>
I've tried to address all concerns and questions in the updated changelog, so, hopefully, now it's clear why do we need this change. Are there any comments, thoughts or objections left? Thanks!
