From: Hirokazu Takahashi <taka@valinux.co.jp>
To: sekharan@us.ibm.com
Cc: kurosawa@valinux.co.jp, ckrm-tech@lists.sourceforge.net,
linux-mm@kvack.org
Subject: Re: [ckrm-tech] [PATCH 0/8] Pzone based CKRM memory resource controller
Date: Wed, 01 Feb 2006 15:16:02 +0900 (JST) [thread overview]
Message-ID: <20060201.151602.71086465.taka@valinux.co.jp> (raw)
In-Reply-To: <20060201053958.CE35B74035@sv1.valinux.co.jp>
Hi Chandra,
>You are welcome. Thanks for the comments.
>
>> I have few questions:
>> - how are shared pages handled ?
>
>Shared pages are accounted to the class that a task in it allocate
>the pages. This behavior is different from the memory resource
>controller in CKRM.
>
>> - what is the plan to support "limit" ?
>
>To be honest, I don't have any specific idea to support "limit" currently.
>Probably the userspace daemon that enlarge "guarantee" to the specified
>"limit" might support the "limit", because "guarantee" in the pzone based
>memory resource controller also works as "limit".
I think that this should be placed outside of Kurosawa's controller.
That would be a kernel thread between CKRM API and the controller,
which collects statistics about pzones to change the size of them
between "guarantee" and "limit". An userspace daemon would be also OK.
To separate balancing pzones code from VM will keep the code simple.
>> - can you provide more information in stats ?
>
>Ok, I'll do that.
>
>> - is it designed to work with cpumeter alone (i.e without ckrm) ?
>
>Maybe it works with cpumeter.
>
>> comment/suggestion:
>> - IMO, moving pages from a class at time of reclassification would be
>> the right thing to do. May be we have to add a pointer to Chris patch
>> and make sure it works as we expect.
>>
>> - instead of adding the pseudo zone related code to the core memory
>> files, you can put them in a separate file.
>
>That's right. But I guess that several static functions in
>mm/page_alloc.c would need to be exported.
>
>> - Documentation on how to configure and use it would be good.
>
>I think so too. I'll write some documents.
Thanks,
Hirokazu Takahashi.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-02-01 6:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 8:04 [PATCH 0/2] " KUROSAWA Takahiro
2006-01-19 8:04 ` [PATCH 1/2] Add the pzone KUROSAWA Takahiro
2006-01-19 18:04 ` Andy Whitcroft
2006-01-19 23:42 ` KUROSAWA Takahiro
2006-01-20 9:17 ` Andy Whitcroft
2006-01-20 7:08 ` KAMEZAWA Hiroyuki
2006-01-20 8:22 ` KUROSAWA Takahiro
2006-01-20 8:30 ` KAMEZAWA Hiroyuki
2006-01-19 8:04 ` [PATCH 2/2] Add CKRM memory resource controller using pzones KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 0/8] Pzone based CKRM memory resource controller KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 1/8] Add the __GFP_NOLRU flag KUROSAWA Takahiro
2006-01-31 18:18 ` [ckrm-tech] " Dave Hansen
2006-02-01 5:06 ` KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 2/8] Keep the number of zones while zone iterator loop KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 3/8] Add for_each_zone_in_node macro KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 4/8] Extract zone specific routines as functions KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 5/8] Add the pzone_create() function KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 6/8] Add the pzone_destroy() function KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 7/8] Make the number of pages in pzones resizable KUROSAWA Takahiro
2006-01-31 2:30 ` [PATCH 8/8] Add a CKRM memory resource controller using pzones KUROSAWA Takahiro
2006-02-01 2:58 ` [ckrm-tech] [PATCH 0/8] Pzone based CKRM memory resource controller chandra seetharaman
2006-02-01 5:39 ` KUROSAWA Takahiro
2006-02-01 6:16 ` Hirokazu Takahashi [this message]
2006-02-02 1:26 ` chandra seetharaman
2006-02-02 3:54 ` KUROSAWA Takahiro
2006-02-03 0:37 ` chandra seetharaman
2006-02-03 0:51 ` KUROSAWA Takahiro
2006-02-03 1:01 ` chandra seetharaman
2006-02-01 3:07 ` chandra seetharaman
2006-02-01 5:54 ` KUROSAWA Takahiro
2006-02-03 1:33 ` KUROSAWA Takahiro
2006-02-03 9:37 ` KUROSAWA Takahiro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060201.151602.71086465.taka@valinux.co.jp \
--to=taka@valinux.co.jp \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=kurosawa@valinux.co.jp \
--cc=linux-mm@kvack.org \
--cc=sekharan@us.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox