All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, willy@infradead.org,
	vdavydov.dev@gmail.com, timmurray@google.com, surenb@google.com,
	mhocko@suse.com, liumartin@google.com, joaodias@google.com,
	hannes@cmpxchg.org, minchan@kernel.org,
	akpm@linux-foundation.org
Subject: [folded-merged] mm-dont-be-stuck-to-rmap-lock-on-reclaim-path-fix.patch removed from -mm tree
Date: Thu, 19 May 2022 14:03:20 -0700	[thread overview]
Message-ID: <20220519210320.BB1D0C385AA@smtp.kernel.org> (raw)


The quilt patch titled
     Subject: mm-dont-be-stuck-to-rmap-lock-on-reclaim-path-fix
has been removed from the -mm tree.  Its filename was
     mm-dont-be-stuck-to-rmap-lock-on-reclaim-path-fix.patch

This patch was dropped because it was folded into mm-dont-be-stuck-to-rmap-lock-on-reclaim-path.patch

------------------------------------------------------
From: Minchan Kim <minchan@kernel.org>
Subject: mm-dont-be-stuck-to-rmap-lock-on-reclaim-path-fix
Date: Wed, 4 May 2022 23:11:04 -0700

add comment, per Matthew

Link: https://lkml.kernel.org/r/YnNqeB5tUf6LZ57b@google.com
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Michal Hocko <mhocko@suse.com>
Cc: John Dias <joaodias@google.com>
Cc: Tim Murray <timmurray@google.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>
Cc: Martin Liu <liumartin@google.com>
Cc: Minchan Kim <minchan@kernel.org>
Cc: Matthew Wilcox <willy@infradead.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/page_idle.c |    4 ++++
 1 file changed, 4 insertions(+)

--- a/mm/page_idle.c~mm-dont-be-stuck-to-rmap-lock-on-reclaim-path-fix
+++ a/mm/page_idle.c
@@ -87,6 +87,10 @@ static void page_idle_clear_pte_refs(str
 {
 	struct folio *folio = page_folio(page);
 
+	/*
+	 * Since rwc.try_lock is unused, rwc is effectively immutable, so we
+	 * can make it static to save some cycles and stack.
+	 */
 	static struct rmap_walk_control rwc = {
 		.rmap_one = page_idle_clear_pte_refs_one,
 		.anon_lock = folio_lock_anon_vma_read,
_

Patches currently in -mm which might be from minchan@kernel.org are

mm-dont-be-stuck-to-rmap-lock-on-reclaim-path.patch


                 reply	other threads:[~2022-05-19 21:03 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=20220519210320.BB1D0C385AA@smtp.kernel.org \
    --to=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=joaodias@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liumartin@google.com \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=timmurray@google.com \
    --cc=vdavydov.dev@gmail.com \
    --cc=willy@infradead.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 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.