From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,surenb@google.com,shli@fb.com,lokeshgidra@google.com,kaleshsingh@google.com,david@redhat.com,gaoxu2@honor.com,akpm@linux-foundation.org
Subject: [to-be-updated] mm-add-lazyfree-folio-to-lru-tail.patch removed from -mm tree
Date: Mon, 09 Sep 2024 15:22:27 -0700 [thread overview]
Message-ID: <20240909222228.529FEC4CEC5@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: add lazyfree folio to lru tail
has been removed from the -mm tree. Its filename was
mm-add-lazyfree-folio-to-lru-tail.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: gaoxu <gaoxu2@honor.com>
Subject: mm: add lazyfree folio to lru tail
Date: Fri, 16 Aug 2024 07:48:01 +0000
Replace lruvec_add_folio with lruvec_add_folio_tail in the lru_lazyfree_fn:
1. The lazy-free folio is added to the LRU_INACTIVE_FILE list. If
it's moved to the LRU tail, it allows for faster release lazy-free
folio and reduces the impact on file refault.
2. When mglru is enabled, the lazy-free folio is reclaimabled and
should be added using lru_gen_add_folio(lruvec, folio, true) instead of
lru_gen_add_folio(lruvec, folio, false) for adding to gen.
With the change in place, workingset_refault_file is reduced by 33% in the
continuous startup testing of the applications in the Android system.
Link: https://lkml.kernel.org/r/f29f64e29c08427b95e3df30a5770056@honor.com
Signed-off-by: gaoxu <gaoxu2@honor.com>
Cc: Kalesh Singh <kaleshsingh@google.com>
Cc: Shaohua Li <shli@fb.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Lokesh Gidra <lokeshgidra@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/swap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/swap.c~mm-add-lazyfree-folio-to-lru-tail
+++ a/mm/swap.c
@@ -641,7 +641,7 @@ static void lru_lazyfree(struct lruvec *
* anonymous folios
*/
folio_clear_swapbacked(folio);
- lruvec_add_folio(lruvec, folio);
+ lruvec_add_folio_tail(lruvec, folio);
__count_vm_events(PGLAZYFREE, nr_pages);
__count_memcg_events(lruvec_memcg(lruvec), PGLAZYFREE, nr_pages);
_
Patches currently in -mm which might be from gaoxu2@honor.com are
reply other threads:[~2024-09-09 22:22 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=20240909222228.529FEC4CEC5@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gaoxu2@honor.com \
--cc=kaleshsingh@google.com \
--cc=lokeshgidra@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=shli@fb.com \
--cc=surenb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.