From: Johannes Weiner <hannes@cmpxchg.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michal Hocko <mhocko@suse.cz>, Hugh Dickins <hughd@google.com>,
Tejun Heo <tj@kernel.org>,
Vladimir Davydov <vdavydov@parallels.com>,
cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: [patch 07/10] mm: memcontrol: remove ordering between pc->mem_cgroup and PageCgroupUsed
Date: Thu, 29 May 2014 12:15:59 -0400 [thread overview]
Message-ID: <1401380162-24121-8-git-send-email-hannes@cmpxchg.org> (raw)
In-Reply-To: <1401380162-24121-1-git-send-email-hannes@cmpxchg.org>
There is a write barrier between setting pc->mem_cgroup and
PageCgroupUsed, which was added to allow LRU operations to lookup the
memcg LRU list of a page without acquiring the page_cgroup lock.
But ever since 38c5d72f3ebe ("memcg: simplify LRU handling by new
rule"), pages are ensured to be off-LRU while charging, so nobody else
is changing LRU state while pc->mem_cgroup is being written, and there
are no read barriers anymore.
Remove the unnecessary write barrier.
Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Michal Hocko <mhocko@suse.cz>
---
mm/memcontrol.c | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 84195a80068c..f71eec597001 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -2842,14 +2842,6 @@ static void __mem_cgroup_commit_charge(struct mem_cgroup *memcg,
}
pc->mem_cgroup = memcg;
- /*
- * We access a page_cgroup asynchronously without lock_page_cgroup().
- * Especially when a page_cgroup is taken from a page, pc->mem_cgroup
- * is accessed after testing USED bit. To make pc->mem_cgroup visible
- * before USED bit, we need memory barrier here.
- * See mem_cgroup_add_lru_list(), etc.
- */
- smp_wmb();
SetPageCgroupUsed(pc);
if (lrucare) {
@@ -3531,7 +3523,6 @@ void mem_cgroup_split_huge_fixup(struct page *head)
for (i = 1; i < HPAGE_PMD_NR; i++) {
pc = head_pc + i;
pc->mem_cgroup = memcg;
- smp_wmb();/* see __commit_charge() */
pc->flags = head_pc->flags & ~PCGF_NOCOPY_AT_SPLIT;
}
__this_cpu_sub(memcg->stat->count[MEM_CGROUP_STAT_RSS_HUGE],
--
1.9.3
--
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:[~2014-05-29 16:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-29 16:15 [patch 0/9] mm: memcontrol: naturalize charge lifetime v2 Johannes Weiner
2014-05-29 16:15 ` [patch 01/10] mm: memcontrol: fold mem_cgroup_do_charge() Johannes Weiner
2014-06-03 12:38 ` Michal Hocko
2014-05-29 16:15 ` [patch 02/10] mm: memcontrol: rearrange charging fast path Johannes Weiner
2014-06-03 12:54 ` Michal Hocko
2014-05-29 16:15 ` [patch 03/10] mm: memcontrol: retry reclaim for oom-disabled and __GFP_NOFAIL charges Johannes Weiner
2014-06-03 13:20 ` Michal Hocko
2014-05-29 16:15 ` [patch 04/10] mm: memcontrol: reclaim at least once for __GFP_NORETRY Johannes Weiner
2014-06-03 13:16 ` Michal Hocko
2014-05-29 16:15 ` [patch 05/10] mm: memcontrol: catch root bypass in move precharge Johannes Weiner
2014-06-03 13:22 ` Michal Hocko
2014-05-29 16:15 ` [patch 06/10] mm: memcontrol: use root_mem_cgroup res_counter Johannes Weiner
2014-06-03 14:11 ` Michal Hocko
2014-05-29 16:15 ` Johannes Weiner [this message]
2014-05-29 16:16 ` [patch 08/10] mm: memcontrol: do not acquire page_cgroup lock for kmem pages Johannes Weiner
2014-05-29 16:16 ` [patch 09/10] mm: memcontrol: rewrite charge API Johannes Weiner
2014-05-29 16:16 ` [patch 10/10] mm: memcontrol: rewrite uncharge API Johannes Weiner
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=1401380162-24121-8-git-send-email-hannes@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=tj@kernel.org \
--cc=vdavydov@parallels.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