From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Michal Hocko <mhocko@suse.cz>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] Make swap accounting default behavior configurable v2
Date: Mon, 15 Nov 2010 07:33:30 +0530 [thread overview]
Message-ID: <20101115020330.GB9882@balbir.in.ibm.com> (raw)
In-Reply-To: <20101115101335.8880fd87.nishimura@mxp.nes.nec.co.jp>
* nishimura@mxp.nes.nec.co.jp <nishimura@mxp.nes.nec.co.jp> [2010-11-15 10:13:35]:
Thanks Nishimura-San
It seems like the motivation for the patch is to allow distros to
enable memory cgroups and swap control, but to have swap control
turned off by default (because we provide default on today)
- is my understanding correct?
--
Three Cheers,
Balbir
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-15 2:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 12:51 [RFC PATCH] Make swap accounting default behavior configurable Michal Hocko
2010-11-11 0:46 ` Daisuke Nishimura
2010-11-11 9:31 ` Michal Hocko
2010-11-12 0:41 ` Daisuke Nishimura
2010-11-12 8:31 ` [RFC PATCH] Make swap accounting default behavior configurable v2 Michal Hocko
2010-11-15 1:13 ` Daisuke Nishimura
2010-11-15 2:03 ` Balbir Singh [this message]
2010-11-15 2:31 ` Daisuke Nishimura
2010-11-15 8:35 ` [RFC PATCH] Make swap accounting default behavior configurable v3 Michal Hocko
2010-11-16 4:48 ` Daisuke Nishimura
2010-11-16 8:15 ` Michal Hocko
2010-11-16 10:03 ` Daisuke Nishimura
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=20101115020330.GB9882@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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;
as well as URLs for NNTP newsgroup(s).