linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: balbir@linux.vnet.ibm.com
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
	"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>,
	"kosaki.motohiro@jp.fujitsu.com" <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: [RFC][PATCH 1/4] memcg: add softlimit interface and utilitiy function.
Date: Mon, 9 Mar 2009 18:07:19 +0900	[thread overview]
Message-ID: <20090309180719.73e5e27d.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090309085423.GJ24321@balbir.in.ibm.com>

On Mon, 9 Mar 2009 14:24:23 +0530
Balbir Singh <balbir@linux.vnet.ibm.com> wrote:

> * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-03-09 17:29:11]:
> 
> > On Mon, 9 Mar 2009 13:14:49 +0530
> > Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
> > 
> > > * KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-03-09 16:39:07]:
> > > 
> > > > From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > > > Adds an interface for defining sotlimit per memcg. (no handler in this patch.)
> > > > softlimit.priority and queue for softlimit is added in the next patch.
> > > > 
> > > > 
> > > > Changelog v1->v2:
> > > >  - For refactoring, divided a patch into 2 part and this patch just
> > > >    involves memory.softlimit interface.
> > > >  - Removed governor-detect routine, it was buggy in design.
> > > > 
> > > > Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> > > > ---
> > > >  mm/memcontrol.c |   62 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
> > > >  1 file changed, 60 insertions(+), 2 deletions(-)
> > > 
> > > 
> > > This patch breaks the semantics of resource counters. We would like to
> > > use resource counters to track all overhead. I've refined my tracking
> > > to an extent that the overhead does not show up at all, unless soft
> > > limits kick in. I oppose keeping soft limits outside of resource
> > > counters.
> > > 
> > 
> > BTW, any other user of res_counter than memcg in future ?
> 
> None so far.. but we once the core controllers are developed (CPU,
> memory), I would expect IO, tasks, number of open files, etc to be
> potential exploiters.
> 
> > I'm afraid that res_counter is decolated as chocolate-cake and will not taste
> > good for people who wants simple counter as simple pancake...
> > 
> 
> 
> I think keeping the design modular has helped. This way we can
> optimize resource counters without touching any controller. Only when
> features are enabled is when people get the chocolate cake feeling,
> not otherwise.
> 

Hmm, maybe reducing overhead as per-cpu counter etc.. is necessary anyway.


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>

  reply	other threads:[~2009-03-09  9:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-09  7:37 [RFC][PATCH] memcg: softlimit (Another one) v3 KAMEZAWA Hiroyuki
2009-03-09  7:39 ` [RFC][PATCH 1/4] memcg: add softlimit interface and utilitiy function KAMEZAWA Hiroyuki
2009-03-09  7:44   ` Balbir Singh
2009-03-09  7:55     ` KAMEZAWA Hiroyuki
2009-03-09  8:48       ` Balbir Singh
2009-03-10  5:53         ` KAMEZAWA Hiroyuki
2009-03-10  8:03           ` Balbir Singh
2009-03-10  8:31           ` Balbir Singh
2009-03-09  8:29     ` KAMEZAWA Hiroyuki
2009-03-09  8:54       ` Balbir Singh
2009-03-09  9:07         ` KAMEZAWA Hiroyuki [this message]
2009-03-09  7:41 ` [RFC][PATCH 2/4] memcg: softlimit priority and victim scheduler KAMEZAWA Hiroyuki
2009-03-09  7:42 ` [RFC][PATCH 3/4] memcg: softlimit caller via kswapd KAMEZAWA Hiroyuki
2009-03-10 19:02   ` Balbir Singh
2009-03-10 23:52     ` KAMEZAWA Hiroyuki
2009-03-12  0:05     ` KOSAKI Motohiro
2009-03-12  0:08       ` KAMEZAWA Hiroyuki
2009-03-09  7:43 ` [RFC][PATCH 4/4] memcg: softlimit documenation 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=20090309180719.73e5e27d.kamezawa.hiroyu@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.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