linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Matthew Wilcox (Oracle)" <willy@infradead.org>
To: linux-mm@kvack.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Kent Overstreet <kent.overstreet@linux.dev>
Subject: [PATCH 1/4] mm/swap: Free non-hugetlb large folios in a batch
Date: Sat,  2 Mar 2024 07:00:27 +0000	[thread overview]
Message-ID: <20240302070031.3108523-2-willy@infradead.org> (raw)
In-Reply-To: <20240302070031.3108523-1-willy@infradead.org>

free_unref_folios() can now handle non-hugetlb large folios, so
keep normal large folios in the batch.  hugetlb folios still need
special treatment (and I think they can be freed this way).

Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
---
 mm/swap.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/mm/swap.c b/mm/swap.c
index 6b697d33fa5b..d1e016e9ee1a 100644
--- a/mm/swap.c
+++ b/mm/swap.c
@@ -158,8 +158,8 @@ void put_pages_list(struct list_head *pages)
 	list_for_each_entry(folio, pages, lru) {
 		if (!folio_put_testzero(folio))
 			continue;
-		if (folio_test_large(folio)) {
-			__folio_put_large(folio);
+		if (folio_test_hugetlb(folio)) {
+			free_huge_folio(folio);
 			continue;
 		}
 		/* LRU flag must be clear because it's passed using the lru */
-- 
2.43.0



  reply	other threads:[~2024-03-02  7:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-02  7:00 [PATCH 0/4] Clean up __folio_put() Matthew Wilcox (Oracle)
2024-03-02  7:00 ` Matthew Wilcox (Oracle) [this message]
2024-03-02  7:00 ` [PATCH 2/4] page_alloc: Combine free_the_page() and free_unref_page() Matthew Wilcox (Oracle)
2024-03-02  7:00 ` [PATCH 3/4] page_alloc: Inline destroy_large_folio() into __folio_put_large() Matthew Wilcox (Oracle)
2024-03-02  7:00 ` [PATCH 4/4] swap: Combine __folio_put_small, __folio_put_large and __folio_put Matthew Wilcox (Oracle)

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=20240302070031.3108523-2-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-mm@kvack.org \
    /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