From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kosaki.motohiro@jp.fujitsu.com
Subject: [PATCH 1/2] memcg: mem_cgroup->prev_priority protected by lock.
Date: Tue, 2 Dec 2008 16:11:07 +0900 (JST) [thread overview]
Message-ID: <20081202160949.1CFE.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
Currently, mem_cgroup doesn't have own lock and almost its member doesn't need.
(e.g. info is protected by zone lock, stat is per cpu variable)
However, there is one explict exception. mem_cgroup->prev_priorit need lock,
but doesn't protect.
Luckly, this is NOT bug because prev_priority isn't used for current reclaim code.
However, we plan to use prev_priority future again.
Therefore, fixing is better.
In addision, we plan to reuse this lock for another member.
Then "misc_lock" name is better than "prev_priority_lock".
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
---
mm/memcontrol.c | 20 +++++++++++++++++++-
1 file changed, 19 insertions(+), 1 deletion(-)
Index: b/mm/memcontrol.c
===================================================================
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -142,6 +142,13 @@ struct mem_cgroup {
*/
struct mem_cgroup_lru_info info;
+ /*
+ Almost mem_cgroup member doesn't need lock.
+ (e.g. info is protected by zone lock, stat is per cpu variable)
+ However, rest few member need explict lock.
+ */
+ spinlock_t misc_lock;
+
int prev_priority; /* for recording reclaim priority */
/*
@@ -393,18 +400,28 @@ int mem_cgroup_calc_mapped_ratio(struct
*/
int mem_cgroup_get_reclaim_priority(struct mem_cgroup *mem)
{
- return mem->prev_priority;
+ int prev_priority;
+
+ spin_lock(&mem->misc_lock);
+ prev_priority = mem->prev_priority;
+ spin_unlock(&mem->misc_lock);
+
+ return prev_priority;
}
void mem_cgroup_note_reclaim_priority(struct mem_cgroup *mem, int priority)
{
+ spin_lock(&mem->misc_lock);
if (priority < mem->prev_priority)
mem->prev_priority = priority;
+ spin_unlock(&mem->misc_lock);
}
void mem_cgroup_record_reclaim_priority(struct mem_cgroup *mem, int priority)
{
+ spin_lock(&mem->misc_lock);
mem->prev_priority = priority;
+ spin_unlock(&mem->misc_lock);
}
/*
@@ -1967,6 +1984,7 @@ mem_cgroup_create(struct cgroup_subsys *
}
mem->last_scanned_child = NULL;
+ spin_lock_init(&mem->misc_lock);
return &mem->css;
free_out:
--
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 reply other threads:[~2008-12-02 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 7:11 KOSAKI Motohiro [this message]
2008-12-02 7:13 ` [PATCH 2/2] memcg: make memory.swappiness file KOSAKI Motohiro
2008-12-02 7:15 ` [PATCH 1/2] memcg: mem_cgroup->prev_priority protected by lock KAMEZAWA Hiroyuki
2008-12-02 7:19 ` KOSAKI Motohiro
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=20081202160949.1CFE.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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