From: Hugh Dickins <hugh@veritas.com>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>,
containers@lists.osdl.org, linux-mm@kvack.org,
balbir@linux.vnet.ibm.com, kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [RFC/PATCH] cgroup swap subsystem
Date: Wed, 5 Mar 2008 14:07:07 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0803051400000.22243@blonde.site> (raw)
In-Reply-To: <47CE5AE2.2050303@openvz.org>
On Wed, 5 Mar 2008, Pavel Emelyanov wrote:
> Daisuke Nishimura wrote:
> >
> > Todo:
> > - rebase new kernel, and split into some patches.
> > - Merge with memory subsystem (if it would be better), or
> > remove dependency on CONFIG_CGROUP_MEM_CONT if possible
> > (needs to make page_cgroup more generic one).
>
> Merge is a must IMHO. I can hardly imagine a situation in which
> someone would need these two separately.
Strongly agree. Nobody's interested in swap as such: it's just
secondary memory, where RAM is primary memory. People want to
control memory as the sum of the two; and I expect they may also
want to control primary memory (all that the current memcg does)
within that. I wonder if such nesting of limits fits easily
into cgroups or will be problematic.
Hugh
--
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-03-05 14:07 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 5:59 [RFC/PATCH] cgroup swap subsystem Daisuke Nishimura
2008-03-05 6:36 ` Paul Menage
2008-03-06 12:20 ` Daisuke Nishimura
2008-03-05 6:53 ` KAMEZAWA Hiroyuki
2008-03-05 21:51 ` Hirokazu Takahashi
2008-03-06 11:45 ` Daisuke Nishimura
2008-03-06 12:25 ` Pavel Emelyanov
2008-03-06 12:56 ` kamezawa.hiroyu
2008-03-07 8:22 ` Daisuke Nishimura
2008-03-12 22:57 ` YAMAMOTO Takashi
2008-03-05 7:03 ` KAMEZAWA Hiroyuki
2008-03-05 7:28 ` Balbir Singh
2008-03-07 4:23 ` Daisuke Nishimura
2008-03-05 8:33 ` Pavel Emelyanov
2008-03-05 8:51 ` Daisuke Nishimura
2008-03-05 14:07 ` Hugh Dickins [this message]
2008-03-05 14:14 ` Pavel Emelyanov
2008-03-06 0:33 ` KAMEZAWA Hiroyuki
2008-03-06 0:35 ` Paul Menage
2008-03-06 8:20 ` Pavel Emelyanov
2008-03-06 8:33 ` KAMEZAWA Hiroyuki
2008-03-06 8:38 ` Pavel Emelyanov
2008-03-06 8:48 ` [Devel] " Paul Menage
2008-03-06 8:50 ` Pavel Emelyanov
2008-03-06 8:52 ` Paul Menage
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=Pine.LNX.4.64.0803051400000.22243@blonde.site \
--to=hugh@veritas.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).