lkml.org 
[lkml]   [2013]   [Feb]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PROBLEM: Crash cgdeleting empty memory cgroups with memory.kmem.limit_in_bytes set
On 02/21/2013 03:00 AM, Tejun Heo wrote:
> (cc'ing cgroup / memcg people and quoting whole body)
>
> Looks like something is going wrong with memcg cache destruction.
> Glauber, any ideas? Also, can we please not use names as generic as
> kmem_cache_destroy_work_func for something specific to memcg? How
> about something like memcg_destroy_cache_workfn?
>
> Thanks.

Steffen,

Is there any chance you could test that using SLAB instead of SLUB?
I haven't manage to reproduce it yet, but I am working on some theories
about why this is happening. If I could at least know if this is likely
a cache problem vs a inner-memcg problem, that would help. The calltrace
is not incredibly helpful, but it does indicate that the problem happens
when freeing cache objects.





\
 
 \ /
  Last update: 2013-02-21 13:01    [W:0.126 / U:0.368 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site