mm: kmem: enable kernel memcg accounting from interrupt contexts
If a memcg to charge can be determined (using remote charging API), there are no reasons to exclude allocations made from an interrupt context from the accounting. Such allocations will pass even if the resulting memcg size will exceed the hard limit, but it will affect the application of the memory pressure and an inability to put the workload under the limit will eventually trigger the OOM. To use active_memcg() helper, memcg_kmem_bypass() is moved back to memcontrol.c. Signed-off-by: Roman Gushchin <guro@fb.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Reviewed-by: Shakeel Butt <shakeelb@google.com> Cc: Johannes Weiner <hannes@cmpxchg.org> Cc: Michal Hocko <mhocko@kernel.org> Link: http://lkml.kernel.org/r/20200827225843.1270629-5-guro@fb.com Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:

committed by
Linus Torvalds

parent
37d5985c00
commit
4127c6504f
@@ -1090,6 +1090,19 @@ static __always_inline struct mem_cgroup *get_active_memcg(void)
|
||||
return memcg;
|
||||
}
|
||||
|
||||
static __always_inline bool memcg_kmem_bypass(void)
|
||||
{
|
||||
/* Allow remote memcg charging from any context. */
|
||||
if (unlikely(active_memcg()))
|
||||
return false;
|
||||
|
||||
/* Memcg to charge can't be determined. */
|
||||
if (in_interrupt() || !current->mm || (current->flags & PF_KTHREAD))
|
||||
return true;
|
||||
|
||||
return false;
|
||||
}
|
||||
|
||||
/**
|
||||
* If active memcg is set, do not fallback to current->mm->memcg.
|
||||
*/
|
||||
|
Reference in New Issue
Block a user