From: Alex Shi <alex.shi@linux.alibaba.com>
To: akpm@linux-foundation.org, mgorman@techsingularity.net,
tj@kernel.org, hughd@google.com, khlebnikov@yandex-team.ru,
daniel.m.jordan@oracle.com, yang.shi@linux.alibaba.com,
willy@infradead.org, hannes@cmpxchg.org, lkp@intel.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
cgroups@vger.kernel.org, shakeelb@google.com,
iamjoonsoo.kim@lge.com, richard.weiyang@gmail.com
Cc: Alex Shi <alex.shi@linux.alibaba.com>
Subject: [PATCH v15 15/21] mm/swap: serialize memcg changes during pagevec_lru_move_fn
Date: Tue, 7 Jul 2020 19:46:47 +0800 [thread overview]
Message-ID: <1594122412-28057-16-git-send-email-alex.shi@linux.alibaba.com> (raw)
In-Reply-To: <1594122412-28057-1-git-send-email-alex.shi@linux.alibaba.com>
Hugh Dickins' found a memcg change bug on original version:
If we want to change the pgdat->lru_lock to memcg's lruvec lock, we have
to serialize mem_cgroup_move_account during pagevec_lru_move_fn. The
possible bad scenario would like:
cpu 0 cpu 1
lruvec = mem_cgroup_page_lruvec()
if (!isolate_lru_page())
mem_cgroup_move_account
spin_lock_irqsave(&lruvec->lru_lock <== wrong lock.
So we need the ClearPageLRU to block isolate_lru_page(), then serialize
the memcg change here.
Reported-by: Hugh Dickins <hughd@google.com>
Signed-off-by: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org
---
mm/swap.c | 30 +++++++++++++++++++++++++++++-
1 file changed, 29 insertions(+), 1 deletion(-)
diff --git a/mm/swap.c b/mm/swap.c
index 5092fe9c8c47..8488b9b25730 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -221,8 +221,14 @@ static void pagevec_lru_move_fn(struct pagevec *pvec,
spin_lock_irqsave(&pgdat->lru_lock, flags);
}
+ /* block memcg migration during page moving between lru */
+ if (!TestClearPageLRU(page))
+ continue;
+
lruvec = mem_cgroup_page_lruvec(page, pgdat);
(*move_fn)(page, lruvec);
+
+ SetPageLRU(page);
}
if (pgdat)
spin_unlock_irqrestore(&pgdat->lru_lock, flags);
@@ -976,7 +982,29 @@ static void __pagevec_lru_add_fn(struct page *page, struct lruvec *lruvec)
*/
void __pagevec_lru_add(struct pagevec *pvec)
{
- pagevec_lru_move_fn(pvec, __pagevec_lru_add_fn);
+ int i;
+ struct pglist_data *pgdat = NULL;
+ struct lruvec *lruvec;
+ unsigned long flags = 0;
+
+ for (i = 0; i < pagevec_count(pvec); i++) {
+ struct page *page = pvec->pages[i];
+ struct pglist_data *pagepgdat = page_pgdat(page);
+
+ if (pagepgdat != pgdat) {
+ if (pgdat)
+ spin_unlock_irqrestore(&pgdat->lru_lock, flags);
+ pgdat = pagepgdat;
+ spin_lock_irqsave(&pgdat->lru_lock, flags);
+ }
+
+ lruvec = mem_cgroup_page_lruvec(page, pgdat);
+ __pagevec_lru_add_fn(page, lruvec);
+ }
+ if (pgdat)
+ spin_unlock_irqrestore(&pgdat->lru_lock, flags);
+ release_pages(pvec->pages, pvec->nr);
+ pagevec_reinit(pvec);
}
/**
--
1.8.3.1
next prev parent reply other threads:[~2020-07-07 11:47 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 11:46 [PATCH v15 00/20] per memcg lock Alex Shi
2020-07-07 11:46 ` [PATCH v15 01/21] mm/vmscan: remove unnecessary lruvec adding Alex Shi
2020-07-07 11:46 ` [PATCH v15 02/21] mm/page_idle: no unlikely double check for idle page counting Alex Shi
2020-07-07 11:46 ` [PATCH v15 03/21] mm/compaction: correct the comments of compact_defer_shift Alex Shi
2020-07-07 11:46 ` [PATCH v15 04/21] mm/compaction: rename compact_deferred as compact_should_defer Alex Shi
2020-07-07 11:46 ` [PATCH v15 05/21] mm/thp: move lru_add_page_tail func to huge_memory.c Alex Shi
2020-07-07 12:00 ` Alex Shi
2020-07-09 15:55 ` Kirill A. Shutemov
2020-07-07 11:46 ` [PATCH v15 06/21] mm/thp: clean up lru_add_page_tail Alex Shi
2020-07-07 11:46 ` [PATCH v15 07/21] mm/thp: narrow lru locking Alex Shi
2020-07-07 11:46 ` [PATCH v15 08/21] mm/memcg: add debug checking in lock_page_memcg Alex Shi
2020-07-07 11:46 ` [PATCH v15 09/21] mm/swap: fold vm event PGROTATED into pagevec_move_tail_fn Alex Shi
2020-07-07 11:46 ` [PATCH v15 10/21] mm/lru: move lru_lock holding in func lru_note_cost_page Alex Shi
2020-07-07 11:46 ` [PATCH v15 11/21] mm/lru: move lock into lru_note_cost Alex Shi
2020-07-07 11:46 ` [PATCH v15 12/21] mm/lru: introduce TestClearPageLRU Alex Shi
2020-07-07 11:46 ` [PATCH v15 13/21] mm/compaction: do page isolation first in compaction Alex Shi
2020-07-07 11:46 ` [PATCH v15 14/21] mm/mlock: reorder isolation sequence during munlock Alex Shi
2020-07-07 11:46 ` Alex Shi [this message]
2020-07-07 11:46 ` [PATCH v15 16/21] mm/lru: replace pgdat lru_lock with lruvec lock Alex Shi
2020-07-07 11:46 ` [PATCH v15 17/21] mm/lru: introduce the relock_page_lruvec function Alex Shi
2020-07-07 11:46 ` [PATCH v15 18/21] mm/vmscan: use relock for move_pages_to_lru Alex Shi
2020-07-07 11:46 ` [PATCH v15 19/21] mm/pgdat: remove pgdat lru_lock Alex Shi
2020-07-07 11:46 ` [PATCH v15 20/21] mm/lru: revise the comments of lru_lock Alex Shi
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=1594122412-28057-16-git-send-email-alex.shi@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=daniel.m.jordan@oracle.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=mgorman@techsingularity.net \
--cc=richard.weiyang@gmail.com \
--cc=shakeelb@google.com \
--cc=tj@kernel.org \
--cc=willy@infradead.org \
--cc=yang.shi@linux.alibaba.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