public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	Balbir Singh <balbir@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: further checking of disabled flag
Date: Mon, 30 Jun 2008 14:05:18 +0800	[thread overview]
Message-ID: <4868779E.9050309@cn.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806290115440.20280@blonde.site>

Hugh Dickins wrote:
> Further adjustments to the mem_cgroup_subsys.disabled tests: add one to
> mem_cgroup_shrink_usage; move mem_cgroup_charge_common's into its callers,
> before they've done any work; and add one to mem_cgroup_move_lists, to
> avoid the overhead of its bit spin locking and unlocking.
> 
> Signed-off-by: Hugh Dickins <hugh@veritas.com>

Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>

> ---
> Should follow mmotm's memcg-clean-up-checking-of-the-disabled-flag.patch
> 

But this needn't follow memcg-clean-up-checking-of-the-disabled-flag.patch,
because this patch is not a fix to it. :)

  parent reply	other threads:[~2008-06-30  6:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29  0:13 [PATCH] memcg: fix shmem_unuse_inode charging Hugh Dickins
2008-06-29  0:14 ` [PATCH] memcg: shmem_getpage release page sooner Hugh Dickins
2008-06-30  2:28   ` KAMEZAWA Hiroyuki
2008-06-29  0:15 ` [PATCH] memcg: mem_cgroup_shrink_usage css_put Hugh Dickins
2008-06-30  2:27   ` KAMEZAWA Hiroyuki
2008-06-30  6:28     ` Balbir Singh
2008-06-29  0:17 ` [PATCH] memcg: further checking of disabled flag Hugh Dickins
2008-06-30  2:26   ` KAMEZAWA Hiroyuki
2008-06-30  6:27     ` Balbir Singh
2008-06-30  6:05   ` Li Zefan [this message]
2008-06-30  2:23 ` [PATCH] memcg: fix shmem_unuse_inode charging KAMEZAWA Hiroyuki
2008-06-30  6:26   ` Balbir Singh

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=4868779E.9050309@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@in.ibm.com \
    --cc=hugh@veritas.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.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