linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH mmotm 2/2] memcg: allow mem.limit bigger than memsw.limit iff unlimited
Date: Thu, 4 Jun 2009 13:31:38 +0900	[thread overview]
Message-ID: <20090604133138.d8286db9.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090603174641.445e3012.kamezawa.hiroyu@jp.fujitsu.com>

On Wed, 3 Jun 2009 17:46:41 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Wed, 3 Jun 2009 14:01:02 +0900
> Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> 
> > On Wed, 3 Jun 2009 12:52:28 +0900, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> > > On Wed, 3 Jun 2009 11:50:27 +0900
> > > Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> > > 
> > > > Now users cannot set mem.limit bigger than memsw.limit.
> > > > This patch allows mem.limit bigger than memsw.limit iff mem.limit==unlimited.
> > > > 
> > > > By this, users can set memsw.limit without setting mem.limit.
> > > > I think it's usefull if users want to limit memsw only.
> > > > They must set mem.limit first and memsw.limit to the same value now for this purpose.
> > > > They can save the first step by this patch.
> > > > 
> > > 
> > > I don't like this. No benefits to users.
> > > The user should know when they set memsw.limit they have to set memory.limit.
> > > This just complicates things.
> > > 
> > Hmm, I think there is a user who cares only limitting logical memory(mem+swap),
> > not physical memory, and wants kswapd to reclaim physical memory when congested. 
> > At least, I'm a such user.
> > 
> > Do you disagree even if I add a file like "memory.allow_limit_memsw_only" ?
> > 
> 
> How about removing memory.limit < memsw.limit condition completely ?
> 
It might be good idea.
IMHO, there is no critical reason it must be checked by kernel, but I'm not sure.

All I wanted to do was "let users who cares only about memsw.limit
ignore mem.limit completely". That's why, I treated only the "unlimited"(not set
mem.limit) case as special.
But, as you say, there is no reason it must be implemented in kernel.
(We can use a middle-ware or something.)

I'll drop this and consider more.


Thanks,
Daisuke Nishimura.

--
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-06-04  4:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  2:45 [PATCH mmotm 0/2] memcg: changes to *.limit_in_bytes Daisuke Nishimura
2009-06-03  2:49 ` [PATCH mmotm 1/2] memcg: add interface to reset limits Daisuke Nishimura
2009-06-03  3:54   ` KAMEZAWA Hiroyuki
2009-06-03  5:16   ` Li Zefan
2009-06-03  5:43     ` Daisuke Nishimura
2009-06-05 13:22       ` [PATCH mmotm] " Daisuke Nishimura
2009-06-05 20:20         ` Andrew Morton
2009-06-03  2:50 ` [PATCH mmotm 2/2] memcg: allow mem.limit bigger than memsw.limit iff unlimited Daisuke Nishimura
2009-06-03  3:52   ` KAMEZAWA Hiroyuki
2009-06-03  5:01     ` Daisuke Nishimura
2009-06-03  8:20       ` KAMEZAWA Hiroyuki
2009-06-03  8:46       ` KAMEZAWA Hiroyuki
2009-06-04  4:31         ` Daisuke Nishimura [this message]

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=20090604133138.d8286db9.nishimura@mxp.nes.nec.co.jp \
    --to=nishimura@mxp.nes.nec.co.jp \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.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