From: <xu.xin16@zte.com.cn>
To: <willy@infradead.org>, <ziy@nvidia.com>, <akpm@linux-foundation.org>
Cc: <ran.xiaokai@zte.com.cn>, <xu.xin16@zte.com.cn>,
<yang.yang29@zte.com.cn>, <mhocko@kernel.org>, <david@redhat.com>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH linux-next] mm: huge_memory: remove is_transparent_hugepage()
Date: Wed, 5 Jun 2024 16:37:31 +0800 (CST) [thread overview]
Message-ID: <20240605163731027tu4GJzm7fzc00snHCyF_3@zte.com.cn> (raw)
From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
is_transparent_hugepage() was first introduced to ensure the page is
2M THP page. After commit de53c05f2ae3 ("mm: add large_rmappable
page flag") and commit fc4d182316bd ("mm: huge_memory: enable debugfs
to split huge pages to any order"), any large folio of mTHP suitable order
can be split, not only 2M THP page.
so the check in split_huge_pages_pid() is not needed here, instead
a folio_test_large() check is sufficient. To ensure a 2M THP folio,
we should use "folio_order(folio) == HPAGE_PMD_ORDER" for now.
As split_huge_pages_pid() is the only user of is_transparent_hugepage(),
we can remove this helper.
Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
---
mm/huge_memory.c | 11 +----------
1 file changed, 1 insertion(+), 10 deletions(-)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 317de2afd371..f1a992945007 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -839,15 +839,6 @@ struct deferred_split *get_deferred_split_queue(struct folio *folio)
}
#endif
-static inline bool is_transparent_hugepage(const struct folio *folio)
-{
- if (!folio_test_large(folio))
- return false;
-
- return is_huge_zero_folio(folio) ||
- folio_test_large_rmappable(folio);
-}
-
static unsigned long __thp_get_unmapped_area(struct file *filp,
unsigned long addr, unsigned long len,
loff_t off, unsigned long flags, unsigned long size,
@@ -3439,7 +3430,7 @@ static int split_huge_pages_pid(int pid, unsigned long vaddr_start,
continue;
folio = page_folio(page);
- if (!is_transparent_hugepage(folio))
+ if (!folio_test_large(folio))
goto next;
if (new_order >= folio_order(folio))
--
2.15.2
reply other threads:[~2024-06-05 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240605163731027tu4GJzm7fzc00snHCyF_3@zte.com.cn \
--to=xu.xin16@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=willy@infradead.org \
--cc=yang.yang29@zte.com.cn \
--cc=ziy@nvidia.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