From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"xemul@openvz.org" <xemul@openvz.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
"yamamoto@valinux.co.jp" <yamamoto@valinux.co.jp>,
"hugh@veritas.com" <hugh@veritas.com>,
"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [RFC][-mm] [0/7] misc memcg patch set
Date: Thu, 3 Jul 2008 11:38:28 +0900 [thread overview]
Message-ID: <20080703113828.f541d562.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20080702210322.518f6c43.kamezawa.hiroyu@jp.fujitsu.com>
On Wed, 2 Jul 2008 21:03:22 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> Other patches in plan (including other guy's)
> - soft-limit (Balbir works.)
> I myself think memcg-background-job patches can copperative with this.
>
> - dirty_ratio for memcg. (haven't written at all)
> Support dirty_ratio for memcg. This will improve OOM avoidance.
>
> - swapiness for memcg (had patches..but have to rewrite.)
> Support swapiness per memcg. (of no use ?)
>
> - swap_controller (Maybe Nishimura works on.)
> The world may change after this...cgroup without swap can appears easily.
>
> - hierarchy (needs more discussion. maybe after OLS?)
> have some pathes, but not in hurry.
>
> - more performance improvements (we need some trick.)
> = Can we remove lock_page_cgroup() ?
> = Can we reduce spinlocks ?
>
> - move resource at task move (needs helps from cgroup)
> We need some magical way. It seems impossible to implement this only by memcg.
>
> - NUMA statistics (needs helps from cgroup)
> It seems dynamic file creation feature or some rule to show array of
> statistics should be defined.
>
> - memory guarantee (soft-mlock.)
> guard parameter against global LRU for saying "Don't reclaim from me more ;("
> Maybe HA Linux people will want this....
>
> Do you have others ?
>
+ hugepage handling.
Currently hugepage is charged as PAGE_SIZE page....it's a BUG.
At first, it seems we have to avoid charging PG_compund page.
(until multi-size page cache is introduced.)
I think hugepage itself is an other resource than memcg deals with. The total
amount ot it is controlled by sysctl.
Should we add hugepage controller or memrlimit controller will handle it ?
Or just ignore hugepage ?
Thanks,
-Kame
--
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:[~2008-07-03 2:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 12:03 KAMEZAWA Hiroyuki
2008-07-02 12:07 ` [RFC][-mm] [1/7] shmem swapcache fix KAMEZAWA Hiroyuki
2008-07-02 12:08 ` [RFC][-mm] [2/7] delete FLAG_CACHE KAMEZAWA Hiroyuki
2008-07-02 12:10 ` [RFC][-mm] [3/7] add shmem page to active list KAMEZAWA Hiroyuki
2008-07-03 0:11 ` KAMEZAWA Hiroyuki
2008-07-03 4:27 ` KAMEZAWA Hiroyuki
2008-07-03 7:03 ` Hugh Dickins
2008-07-03 7:43 ` KAMEZAWA Hiroyuki
2008-07-03 22:28 ` Hugh Dickins
2008-07-04 0:47 ` KAMEZAWA Hiroyuki
2008-07-02 12:12 ` [RFC][-mm] [4/7] handle limit change KAMEZAWA Hiroyuki
2008-07-02 12:13 ` [RFC][-mm] [5/7] reduce usage at " KAMEZAWA Hiroyuki
2008-07-02 12:15 ` [RFC][-mm] [6/7] res_counter distance to limit KAMEZAWA Hiroyuki
2008-07-02 19:19 ` Paul Menage
2008-07-02 23:57 ` KAMEZAWA Hiroyuki
2008-07-02 12:17 ` [RFC][-mm] [7/7] background job for memcg KAMEZAWA Hiroyuki
2008-07-02 14:23 ` [RFC][-mm] [0/7] misc memcg patch set Daisuke Nishimura
2008-07-02 16:31 ` KOSAKI Motohiro
2008-07-02 23:56 ` KAMEZAWA Hiroyuki
2008-07-03 2:38 ` KAMEZAWA Hiroyuki [this message]
2008-07-03 3:06 ` KAMEZAWA Hiroyuki
2008-07-03 9:07 ` Balbir Singh
2008-07-03 9:54 ` KAMEZAWA Hiroyuki
2008-07-11 8:38 ` KAMEZAWA Hiroyuki
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=20080703113828.f541d562.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/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