On 11/02/2012 08:25 PM, JoonSoo Kim wrote:
> Hello, Glauber.
>
> 2012/11/2 Glauber Costa :
>> On 11/02/2012 04:04 AM, Andrew Morton wrote:
>>> On Thu, 1 Nov 2012 16:07:16 +0400
>>> Glauber Costa wrote:
>>>
Hi,
This work introduces the kernel memory controller for memcg. Unlike
>>
On 11/03/2012 12:06 AM, Tejun Heo wrote:
> Hey, Joonsoo.
>
> On Sat, Nov 03, 2012 at 04:25:59AM +0900, JoonSoo Kim wrote:
>> I am worrying about data cache footprint which is possibly caused by
>> this patchset, especially slab implementation.
>> If there are several memcg cgroups, each cgroup has
On Fri, Nov 2, 2012 at 12:41 AM, Glauber Costa wrote:
> On 11/02/2012 04:04 AM, Andrew Morton wrote:
>> On Thu, 1 Nov 2012 16:07:16 +0400
>> Glauber Costa wrote:
>>
>>> Hi,
>>>
>>> This work introduces the kernel memory controller for memcg. Unlike previous
>>> submissions, this includes the who
Hey, Joonsoo.
On Sat, Nov 03, 2012 at 04:25:59AM +0900, JoonSoo Kim wrote:
> I am worrying about data cache footprint which is possibly caused by
> this patchset, especially slab implementation.
> If there are several memcg cgroups, each cgroup has it's own kmem_caches.
> When each group do slab-i
Hello, Glauber.
2012/11/2 Glauber Costa :
> On 11/02/2012 04:04 AM, Andrew Morton wrote:
>> On Thu, 1 Nov 2012 16:07:16 +0400
>> Glauber Costa wrote:
>>
>>> Hi,
>>>
>>> This work introduces the kernel memory controller for memcg. Unlike previous
>>> submissions, this includes the whole controlle
On Fri, Nov 2, 2012 at 2:04 AM, Andrew Morton wrote:
> One thing:
>
>> Numbers can be found at https://lkml.org/lkml/2012/9/13/239
>
> You claim in the above that the fork worload is 'slab intensive". Or
> at least, you seem to - it's a bit fuzzy.
>
> But how slab intensive is it, really?
>
> Wha
On 11/02/2012 04:04 AM, Andrew Morton wrote:
> On Thu, 1 Nov 2012 16:07:16 +0400
> Glauber Costa wrote:
>
>> Hi,
>>
>> This work introduces the kernel memory controller for memcg. Unlike previous
>> submissions, this includes the whole controller, comprised of slab and stack
>> memory.
>
> I'm
On Thu, 1 Nov 2012 16:07:16 +0400
Glauber Costa wrote:
> Hi,
>
> This work introduces the kernel memory controller for memcg. Unlike previous
> submissions, this includes the whole controller, comprised of slab and stack
> memory.
I'm in the middle of (re)reading all this. Meanwhile I'll push
Hi,
This work introduces the kernel memory controller for memcg. Unlike previous
submissions, this includes the whole controller, comprised of slab and stack
memory.
Slab-specific considerations: I've modified the kmem_cache_free() mechanism
so we would have the code in a single location. It is t
9 matches
Mail list logo