From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Hugh Dickins <hugh@veritas.com>,
Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@in.ibm.com>, Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: further checking of disabled flag
Date: Mon, 30 Jun 2008 11:57:05 +0530 [thread overview]
Message-ID: <48687CB9.4090505@linux.vnet.ibm.com> (raw)
In-Reply-To: <20080630112608.94fe4762.kamezawa.hiroyu@jp.fujitsu.com>
KAMEZAWA Hiroyuki wrote:
> On Sun, 29 Jun 2008 01:17:17 +0100 (BST)
> Hugh Dickins <hugh@veritas.com> 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>
>
> seems better
>
> Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Acked-by: Balbir Singh <balbir@linux.vnet.ibm.com>
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-06-30 6:27 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 [this message]
2008-06-30 6:05 ` Li Zefan
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=48687CB9.4090505@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.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 \
--cc=lizf@cn.fujitsu.com \
/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