2007-08-08 03:49:46

by Kamezawa Hiroyuki

[permalink] [raw]
Subject: Re: [-mm PATCH 0/9] Memory controller introduction (v4)

On Sat, 28 Jul 2007 01:39:37 +0530
Balbir Singh <[email protected]> wrote:
> At OLS, the resource management BOF, it was discussed that we need to manage
> RSS and unmapped page cache together. This patchset is a step towards that
>
Can I make a question ? Why limiting RSS instead of # of used pages per
container ? Maybe bacause of shared pages between container....
I'm sorry that I don't have much knowledge about history of this work.
If already discussed, the pointer to log is helpful.

Thanks,
-Kame


2007-08-08 07:50:12

by Kamezawa Hiroyuki

[permalink] [raw]
Subject: Re: [-mm PATCH 0/9] Memory controller introduction (v4)

On Wed, 8 Aug 2007 12:51:39 +0900
KAMEZAWA Hiroyuki <[email protected]> wrote:

> On Sat, 28 Jul 2007 01:39:37 +0530
> Balbir Singh <[email protected]> wrote:
> > At OLS, the resource management BOF, it was discussed that we need to manage
> > RSS and unmapped page cache together. This patchset is a step towards that
> >
> Can I make a question ? Why limiting RSS instead of # of used pages per
> container ? Maybe bacause of shared pages between container....
Sorry....Ignore above question.
I didn't understand what mem_container_charge() accounts and limits.
It controls # of meta_pages.

Sorry,
-Kame

2007-08-10 04:50:20

by Vaidyanathan Srinivasan

[permalink] [raw]
Subject: Re: [-mm PATCH 0/9] Memory controller introduction (v4)


KAMEZAWA Hiroyuki wrote:
> On Wed, 8 Aug 2007 12:51:39 +0900
> KAMEZAWA Hiroyuki <[email protected]> wrote:
>
>> On Sat, 28 Jul 2007 01:39:37 +0530
>> Balbir Singh <[email protected]> wrote:
>>> At OLS, the resource management BOF, it was discussed that we need to manage
>>> RSS and unmapped page cache together. This patchset is a step towards that
>>>
>> Can I make a question ? Why limiting RSS instead of # of used pages per
>> container ? Maybe bacause of shared pages between container....
> Sorry....Ignore above question.
> I didn't understand what mem_container_charge() accounts and limits.
> It controls # of meta_pages.

Hi Kame,

Actually the number of pages resident in memory brought in by a
container is charged. However each such page will have a meta_page
allocated to keep the extra data.

Yes, the accounting counts the number of meta_page which is same as
the number of mapped and unmapped (pagecache) pages brought into the
system memory by this container. Whether pagecache pages should be
included or not is configurable per container through the 'type' file
in containerfs.

--Vaidy