linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Pavel Emelyanov <xemul@openvz.org>,
	Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
	Linux Containers <containers@lists.osdl.org>,
	Linux MM <linux-mm@kvack.org>
Subject: Re: [PATCH 2/2] Make res_counter hierarchical
Date: Tue, 11 Mar 2008 08:56:08 -0700	[thread overview]
Message-ID: <6599ad830803110856j5333f032n2e26fb51111a839c@mail.gmail.com> (raw)
In-Reply-To: <47D64E0A.3090907@linux.vnet.ibm.com>

On Tue, Mar 11, 2008 at 2:16 AM, Balbir Singh <balbir@linux.vnet.ibm.com> wrote:
>
> Paul Menage wrote:
>  > On Tue, Mar 11, 2008 at 2:13 AM, KAMEZAWA Hiroyuki
>  > <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>  >>  or remove all relationship among counters of *different* type of resources.
>  >>  user-land-daemon will do enough jobs.
>  >>
>  >
>  > Yes, that would be my preferred choice, if people agree that
>  > hierarchically limiting overall virtual memory isn't useful. (I don't
>  > think I have a use for it myself).
>  >
>
>  Virtual limits are very useful. I have a patch ready to send out.
>  They limit the amount of paging a cgroup can do (virtual limit - RSS limit).

Ah, from this should I assume that you're talking about virtual
address space limits, not virtual memory limits?

My comment above was referring to Pavel's proposal to limit total
virtual memory (RAM + swap) for a cgroup, and then limit swap as a
subset of that, which basically makes it impossible to limit the RAM
usage of cgroups properly if you also want to allow swap usage.

Virtual address space limits are somewhat orthogonal to that.

Paul

--
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>

  parent reply	other threads:[~2008-03-11 15:56 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 15:32 [PATCH 2/2] Make res_counter hierarchical Pavel Emelyanov
2008-03-08  4:45 ` KAMEZAWA Hiroyuki
2008-03-11  8:15   ` Pavel Emelyanov
2008-03-11  8:32     ` KAMEZAWA Hiroyuki
2008-03-11  8:38       ` Pavel Emelyanov
2008-03-11  9:03         ` Daisuke Nishimura
2008-03-11  9:07         ` KAMEZAWA Hiroyuki
2008-03-11  8:57     ` Paul Menage
2008-03-11  9:13       ` KAMEZAWA Hiroyuki
2008-03-11  9:11         ` Paul Menage
2008-03-11  9:16           ` Balbir Singh
2008-03-11  9:39             ` KAMEZAWA Hiroyuki
2008-03-11  9:53               ` Balbir Singh
2008-03-11 10:03                 ` KAMEZAWA Hiroyuki
2008-03-11 15:56             ` Paul Menage [this message]
2008-03-11 15:59               ` Balbir Singh
2008-03-08 19:06 ` Balbir Singh
2008-03-11  8:17   ` Pavel Emelyanov
2008-03-11  8:24     ` Balbir Singh
2008-03-11  8:40       ` Pavel Emelyanov
2008-03-12 23:05 ` YAMAMOTO Takashi
2008-03-12 23:36   ` YAMAMOTO Takashi
2008-03-13  8:56   ` Pavel Emelyanov
     [not found] ` <47D16004.7050204-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-04-02 15:26   ` Balbir Singh
     [not found]     ` <47F3A5BF.1080301-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2008-04-03 12:26       ` Pavel Emelyanov

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=6599ad830803110856j5333f032n2e26fb51111a839c@mail.gmail.com \
    --to=menage@google.com \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=containers@lists.osdl.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=nishimura@mxp.nes.nec.co.jp \
    --cc=xemul@openvz.org \
    /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;
as well as URLs for NNTP newsgroup(s).