From: Luiz Capitulino <luizcap@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
david@redhat.com, yuzhao@google.com, pasha.tatashin@soleen.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
muchun.song@linux.dev, luizcap@redhat.com
Subject: [PATCH 4/4] mm: page_ext: make page_ext_next() private to page_ext
Date: Tue, 18 Feb 2025 21:17:50 -0500 [thread overview]
Message-ID: <5794ff5b322febd376728c8e22c802c15827dcc8.1739931468.git.luizcap@redhat.com> (raw)
In-Reply-To: <cover.1739931468.git.luizcap@redhat.com>
Previous commits removed page_ext_next() use from page_ext clients. Make
it private.
Fixes: cf54f310d0d3 ("mm/hugetlb: use __GFP_COMP for gigantic folios")
Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
---
include/linux/page_ext.h | 7 -------
mm/page_ext.c | 7 +++++++
2 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/include/linux/page_ext.h b/include/linux/page_ext.h
index a99da12e59fa7..3a4f0f825aa59 100644
--- a/include/linux/page_ext.h
+++ b/include/linux/page_ext.h
@@ -101,13 +101,6 @@ static inline void *page_ext_data(struct page_ext *page_ext,
return (void *)(page_ext) + ops->offset;
}
-static inline struct page_ext *page_ext_next(struct page_ext *curr)
-{
- void *next = curr;
- next += page_ext_size;
- return next;
-}
-
struct page_ext_iter {
unsigned long pfn;
unsigned long index;
diff --git a/mm/page_ext.c b/mm/page_ext.c
index 508deb04d5ead..f9e515d353005 100644
--- a/mm/page_ext.c
+++ b/mm/page_ext.c
@@ -567,6 +567,13 @@ struct page_ext *page_ext_iter_begin(struct page_ext_iter *iter, struct page *pa
return iter->page_ext;
}
+static struct page_ext *page_ext_next(struct page_ext *curr)
+{
+ void *next = curr;
+ next += page_ext_size;
+ return next;
+}
+
/**
* page_ext_iter_next() - Get next page extension
* @iter: page extension iterator.
--
2.48.1
next prev parent reply other threads:[~2025-02-19 2:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 2:17 [PATCH 0/4] mm: page_ext: Introduce new iteration API Luiz Capitulino
2025-02-19 2:17 ` [PATCH 1/4] mm: page_ext: add an iteration API for page extensions Luiz Capitulino
2025-02-20 10:59 ` David Hildenbrand
2025-02-20 20:36 ` Luiz Capitulino
2025-02-20 20:45 ` David Hildenbrand
2025-02-20 20:47 ` David Hildenbrand
2025-02-20 21:12 ` Luiz Capitulino
2025-02-19 2:17 ` [PATCH 2/4] mm: page_table_check: use new iteration API Luiz Capitulino
2025-02-20 11:05 ` David Hildenbrand
2025-02-20 20:37 ` Luiz Capitulino
2025-02-19 2:17 ` [PATCH 3/4] mm: page_owner: " Luiz Capitulino
2025-02-19 2:17 ` Luiz Capitulino [this message]
2025-02-19 23:52 ` [PATCH 0/4] mm: page_ext: Introduce " Andrew Morton
2025-02-20 10:49 ` David Hildenbrand
2025-02-20 20:23 ` Luiz Capitulino
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=5794ff5b322febd376728c8e22c802c15827dcc8.1739931468.git.luizcap@redhat.com \
--to=luizcap@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=muchun.song@linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=yuzhao@google.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