From: Yu Zhao <yuzhao@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Alexander Duyck" <alexander.h.duyck@linux.intel.com>,
"Huang Ying" <ying.huang@intel.com>,
"David Hildenbrand" <david@redhat.com>,
"Michal Hocko" <mhocko@suse.com>,
"Yang Shi" <yang.shi@linux.alibaba.com>, "Qian Cai" <cai@lca.pw>,
"Mel Gorman" <mgorman@suse.de>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Hugh Dickins" <hughd@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
"Joonsoo Kim" <iamjoonsoo.kim@lge.com>,
"Yu Zhao" <yuzhao@google.com>
Subject: [PATCH v2 2/3] mm: remove superfluous __ClearPageActive()
Date: Tue, 18 Aug 2020 12:47:03 -0600 [thread overview]
Message-ID: <20200818184704.3625199-2-yuzhao@google.com> (raw)
In-Reply-To: <20200818184704.3625199-1-yuzhao@google.com>
To activate a page, mark_page_accessed() always holds a reference
on it. It either gets a new reference when adding a page to
lru_pvecs.activate_page or reuses an existing one it previously
got when it added a page to lru_pvecs.lru_add. So it doesn't call
SetPageActive() on a page that doesn't have any reference left.
Therefore, the race is impossible these days (I didn't brother to
dig into its history).
For other paths, namely reclaim and migration, a reference count is
always held while calling SetPageActive() on a page.
SetPageSlabPfmemalloc() also uses SetPageActive(), but it's irrelevant
to LRU pages.
Signed-off-by: Yu Zhao <yuzhao@google.com>
---
mm/memremap.c | 2 --
mm/swap.c | 2 --
2 files changed, 4 deletions(-)
diff --git a/mm/memremap.c b/mm/memremap.c
index 03e38b7a38f1..3a06eb91cb59 100644
--- a/mm/memremap.c
+++ b/mm/memremap.c
@@ -451,8 +451,6 @@ void free_devmap_managed_page(struct page *page)
return;
}
- /* Clear Active bit in case of parallel mark_page_accessed */
- __ClearPageActive(page);
__ClearPageWaiters(page);
mem_cgroup_uncharge(page);
diff --git a/mm/swap.c b/mm/swap.c
index 25c4043491b3..999a84dbe12c 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -900,8 +900,6 @@ void release_pages(struct page **pages, int nr)
del_page_from_lru_list(page, lruvec, page_off_lru(page));
}
- /* Clear Active bit in case of parallel mark_page_accessed */
- __ClearPageActive(page);
__ClearPageWaiters(page);
list_add(&page->lru, &pages_to_free);
--
2.28.0.220.ged08abb693-goog
next prev parent reply other threads:[~2020-08-18 18:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 18:47 [PATCH v2 1/3] mm: remove activate_page() from unuse_pte() Yu Zhao
2020-08-18 18:47 ` Yu Zhao [this message]
2020-08-19 23:04 ` [PATCH v2 2/3] mm: remove superfluous __ClearPageActive() Yang Shi
2020-08-18 18:47 ` [PATCH v2 3/3] mm: remove superfluous __ClearPageWaiters() Yu Zhao
2020-08-19 23:06 ` Yang Shi
2020-08-19 23:39 ` Yu Zhao
2020-08-20 0:16 ` Yang Shi
2020-08-20 6:18 ` Michal Hocko
2020-08-20 8:12 ` Yu Zhao
2020-08-19 22:16 ` [PATCH v2 1/3] mm: remove activate_page() from unuse_pte() Yang 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=20200818184704.3625199-2-yuzhao@google.com \
--to=yuzhao@google.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=cai@lca.pw \
--cc=david@redhat.com \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=yang.shi@linux.alibaba.com \
--cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).