Thread (28 messages) 28 messages, 5 authors, 2025-01-15

Re: [PATCH 3/8] mm/zswap: Use PG_dropbehind instead of PG_reclaim

From: David Hildenbrand <hidden>
Date: 2025-01-13 10:06:58
Also in: dri-devel, intel-gfx, linux-fsdevel, linux-mm, lkml

On 13.01.25 10:34, Kirill A. Shutemov wrote:
quoted hunk ↗ jump to hunk
The recently introduced PG_dropbehind allows for freeing folios
immediately after writeback. Unlike PG_reclaim, it does not need vmscan
to be involved to get the folio freed.

Instead of using folio_set_reclaim(), use folio_set_dropbehind() in
zswap_writeback_entry().

Signed-off-by: Kirill A. Shutemov <redacted>
---
  mm/zswap.c | 4 ++--
  1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/zswap.c b/mm/zswap.c
index 167ae641379f..c20bad0b0978 100644
--- a/mm/zswap.c
+++ b/mm/zswap.c
@@ -1096,8 +1096,8 @@ static int zswap_writeback_entry(struct zswap_entry *entry,
  	/* folio is up to date */
  	folio_mark_uptodate(folio);
  
-	/* move it to the tail of the inactive list after end_writeback */
-	folio_set_reclaim(folio);
+	/* free the folio after writeback */
+	folio_set_dropbehind(folio);
Acked-by: David Hildenbrand <redacted>

-- 
Cheers,

David / dhildenb
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help