From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
nishimura@mxp.nes.nec.co.jp, kosaki.motohiro@jp.fujitsu.com,
menage@google.com, prarit@redhat.com, andi.kleen@intel.com,
xemul@openvz.org, lizf@cn.fujitsu.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] Help Resource Counters Scale better (v4.1)
Date: Wed, 12 Aug 2009 22:49:40 +0530 [thread overview]
Message-ID: <20090812171940.GD5087@balbir.in.ibm.com> (raw)
In-Reply-To: <49a88ef4a1ba9ec9426febe9e3633b89.squirrel@webmail-b.css.fujitsu.com>
* KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> [2009-08-13 01:28:57]:
> Balbir Singh wrote:
> > Hi, Andrew,
> >
> > Does this look better, could you please replace the older patch with
> > this one.
> >
> > 1. I did a quick compile test
> > 2. Ran scripts/checkpatch.pl
> >
>
> In general, seems reasonable to me as quick hack for root cgroup.
> thank you.
>
> Reviewed-by: KAMEAZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
>
Thanks, yes, we still need to do the percpu counter work, but this
will give us breathing space to do it correctly and define strict and
non-strict accounting.
> Finally, we'll have to do some rework for light-weight res_counter.
> But yes, it will take some amount of time.
> My only concern is account leak, but, if some leak, it's current code's
> bug, not this patch.
>
Yeah.. we'll need to check for that.
> And..hmm...I like following style other than open-coded.
> ==
> int mem_coutner_charge(struct mem_cgroup *mem)
> {
> if (mem_cgroup_is_root(mem))
> return 0; // always success
> return res_counter_charge(....)
> }
> ==
> But maybe nitpick.
>
Yes, we can refactor for simplication, but we'll need some exceptions.
I'll do that as an add-on patch.
--
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-08-12 17:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 14:44 Help Resource Counters Scale better (v4) Balbir Singh
2009-08-11 14:54 ` Prarit Bhargava
2009-08-11 15:00 ` Balbir Singh
2009-08-11 15:11 ` Prarit Bhargava
2009-08-11 15:14 ` Prarit Bhargava
2009-08-11 15:20 ` Andi Kleen
2009-08-11 15:21 ` Prarit Bhargava
2009-08-11 16:52 ` Balbir Singh
2009-08-11 23:31 ` Andrew Morton
2009-08-12 2:34 ` Daisuke Nishimura
2009-08-12 3:56 ` Balbir Singh
2009-08-12 3:57 ` Balbir Singh
2009-08-12 4:57 ` [PATCH] Help Resource Counters Scale better (v4.1) Balbir Singh
2009-08-12 10:53 ` Prarit Bhargava
2009-08-12 16:19 ` KAMEZAWA Hiroyuki
2009-08-12 16:28 ` KAMEZAWA Hiroyuki
2009-08-12 17:19 ` Balbir Singh [this message]
2009-08-13 1:03 ` Daisuke Nishimura
2009-08-13 3:33 ` Balbir Singh
2009-08-13 5:08 ` 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=20090812171940.GD5087@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=andi.kleen@intel.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=prarit@redhat.com \
--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