linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Luiz Capitulino <luizcap@redhat.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	david@redhat.com, yuzhao@google.com
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org,
	muchun.song@linux.dev, lcapitulino@gmail.com, luizcap@redhat.com
Subject: [RFC 4/4] mm: page_ext: drop page_ext_next()
Date: Fri, 24 Jan 2025 16:37:54 -0500	[thread overview]
Message-ID: <3604c0ceeb0942b25ef645f4b74154c0122149f4.1737754625.git.luizcap@redhat.com> (raw)
In-Reply-To: <cover.1737754625.git.luizcap@redhat.com>

Previous commits converted users to the new page extension iteration API.

TODO: We can use this implementation for flatmem.

Fixes: e98337d11bbd ("mm/contig_alloc: support __GFP_COMP")
Signed-off-by: Luiz Capitulino <luizcap@redhat.com>
---
 include/linux/page_ext.h | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/include/linux/page_ext.h b/include/linux/page_ext.h
index df904544d3fac..4bbc6638fe14f 100644
--- a/include/linux/page_ext.h
+++ b/include/linux/page_ext.h
@@ -86,13 +86,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;
 	struct page_ext *page_ext;
-- 
2.47.1



      parent reply	other threads:[~2025-01-24 21:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 21:37 [RFC 0/4] mm: page_ext: Fix crash when reserving 1G pages Luiz Capitulino
2025-01-24 21:37 ` [RFC 1/4] mm: page_ext: add an iteration API for page extensions Luiz Capitulino
2025-02-11 15:25   ` David Hildenbrand
2025-02-11 16:07     ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 2/4] mm: page_owner: use new iteration API Luiz Capitulino
2025-02-11 15:15   ` David Hildenbrand
2025-02-11 16:00     ` Luiz Capitulino
2025-01-24 21:37 ` [RFC 3/4] mm: page_table_check: " Luiz Capitulino
2025-02-11 15:09   ` David Hildenbrand
2025-01-24 21:37 ` Luiz Capitulino [this message]

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=3604c0ceeb0942b25ef645f4b74154c0122149f4.1737754625.git.luizcap@redhat.com \
    --to=luizcap@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=lcapitulino@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=muchun.song@linux.dev \
    --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