diff options
| author | KOSAKI Motohiro | 2009-01-08 03:08:23 +0100 |
|---|---|---|
| committer | Linus Torvalds | 2009-01-08 17:31:08 +0100 |
| commit | 2733c06ac864ed40b9dfbbd5270f3f16949bd4a1 (patch) | |
| tree | 4847ad04739d6a25dede0e0329295c15cbb79dda /mm/vmscan.c | |
| parent | memcg: rename scan global lru (diff) | |
| download | kernel-qcow2-linux-2733c06ac864ed40b9dfbbd5270f3f16949bd4a1.tar.gz kernel-qcow2-linux-2733c06ac864ed40b9dfbbd5270f3f16949bd4a1.tar.xz kernel-qcow2-linux-2733c06ac864ed40b9dfbbd5270f3f16949bd4a1.zip | |
memcg: protect prev_priority
Currently, mem_cgroup doesn't have own lock and almost its member doesn't
need. (e.g. mem_cgroup->info is protected by zone lock, mem_cgroup->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 addition, we plan to reuse this lock for another member. Then
"reclaim_param_lock" name is better than "prev_priority_lock".
Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Signed-off-by: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Balbir Singh <balbir@in.ibm.com>
Cc: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Hugh Dickins <hugh@veritas.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'mm/vmscan.c')
0 files changed, 0 insertions, 0 deletions