From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
nishimura@mxp.nes.nec.co.jp,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, lizf@cn.fujitsu.com
Subject: Re: [PATCH] use css id in swap cgroup for saving memory v5
Date: Wed, 11 Mar 2009 22:46:37 +0530 [thread overview]
Message-ID: <20090311171637.GF16769@balbir.in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0903111041260.16964@blonde.anvils>
* Hugh Dickins <hugh@veritas.com> [2009-03-11 11:05:55]:
> Sorry, you'd prefer my input on the rest, which I've not studied, but ...
>
> On Wed, 11 Mar 2009, KAMEZAWA Hiroyuki wrote:
> ...
> >
> > @@ -432,7 +428,7 @@ int swap_cgroup_swapon(int type, unsigne
> >
> > printk(KERN_INFO
> > "swap_cgroup: uses %ld bytes of vmalloc for pointer array space"
> > - " and %ld bytes to hold mem_cgroup pointers on swap\n",
> > + " and %ld bytes to hold mem_cgroup information per swap ents\n",
> > array_size, length * PAGE_SIZE);
> > printk(KERN_INFO
> > "swap_cgroup can be disabled by noswapaccount boot option.\n");
>
> ... I do get very irritated by all the screenspace these messages take
> up every time I swapon. I can see that you're following a page_cgroup
> precedent, one which never bothered me because it got buried in dmesg;
> and most other people wouldn't be doing swapon very often, and wouldn't
> be logging to a visible screen ... but is there any chance of putting an
> approximation to this info in the CGROUP_MEM_RES_CTRL_SWAP Kconfig help
> text and removing these runtime messages? How do other people feel?
>
We could just print out the numbers and point to the Documentation for
the user to look at.
> I'm also disappointed that we invented such a tortuously generic boot
> option as "cgroup_disable=memory", then departed from it when the very
> first extension "noswapaccount" was required. "cgroup_disable=swap"?
> Probably too late.
>
Good suggestion and it makes things more consistent for the end user.
It might be too early to start obsoleting noswapaccount?
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-11 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 1:07 [BUGFIX][PATCH] memcg: charge swapcache to proper memcg Daisuke Nishimura
2009-03-10 2:35 ` KAMEZAWA Hiroyuki
2009-03-10 3:18 ` Daisuke Nishimura
2009-03-10 3:42 ` KAMEZAWA Hiroyuki
2009-03-10 4:33 ` KAMEZAWA Hiroyuki
2009-03-10 4:47 ` Daisuke Nishimura
2009-03-10 5:04 ` KAMEZAWA Hiroyuki
2009-03-10 6:38 ` Daisuke Nishimura
2009-03-10 6:56 ` KAMEZAWA Hiroyuki
2009-03-10 23:08 ` Andrew Morton
2009-03-10 23:53 ` KAMEZAWA Hiroyuki
2009-03-11 0:43 ` nishimura
2009-03-11 0:47 ` KAMEZAWA Hiroyuki
2009-03-11 3:04 ` [PATCH] use css id in swap cgroup for saving memory v5 KAMEZAWA Hiroyuki
2009-03-11 11:05 ` Hugh Dickins
2009-03-11 17:16 ` Balbir Singh [this message]
2009-03-11 23:46 ` KAMEZAWA Hiroyuki
2009-03-11 23:50 ` KAMEZAWA Hiroyuki
2009-03-16 22:25 ` Hugh Dickins
2009-03-19 0:44 ` [PATCH] memcg remvoe redundant message at swapon 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=20090311171637.GF16769@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--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