From: Dev Jain <dev.jain@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
ljs@kernel.org, muchun.song@linux.dev, osalvador@suse.de,
riel@surriel.com, liam@infradead.org, vbabka@kernel.org,
harry@kernel.org, jannh@google.com, lance.yang@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v2 5/5] mm/rmap: add anon folio unmap dispatcher
Date: Sat, 11 Jul 2026 17:44:49 +0530 [thread overview]
Message-ID: <7b21094b-fb68-4cb2-8df6-30f6b6dcf0c3@arm.com> (raw)
In-Reply-To: <20260710173519.d7659f9705afa37ad62e7bbb@linux-foundation.org>
On 11/07/26 6:05 am, Andrew Morton wrote:
> On Fri, 10 Jul 2026 18:43:14 +0530 Dev Jain <dev.jain@arm.com> wrote:
>
>> Andrew, could you you squash this diff:
>
> I think I'll await v3, please. I'm getting a big reject in rmap.c and
> methinks we're all a bit firehosed at present.
Okay.
>
> Are we all agreed that we'll be "batching anonymous large folio
> unmapping to optimize it"? If not, is this series pointful?
Even in the impossible case that we don't go ahead with the batching,
this is useful on its own. Just see what try_to_unmap_one looks before
and after :)
>
prev parent reply other threads:[~2026-07-11 12:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 5:59 [PATCH v2 0/5] mm/rmap: Refactor try_to_unmap_one Dev Jain
2026-07-10 5:59 ` [PATCH v2 1/5] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-07-10 12:22 ` David Hildenbrand (Arm)
2026-07-10 13:14 ` Dev Jain
2026-07-10 5:59 ` [PATCH v2 2/5] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-07-10 13:16 ` Dev Jain
2026-07-10 5:59 ` [PATCH v2 3/5] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-07-10 5:59 ` [PATCH v2 4/5] mm/rmap: refactor anon folio unmap in try_to_unmap_one Dev Jain
2026-07-10 5:59 ` [PATCH v2 5/5] mm/rmap: add anon folio unmap dispatcher Dev Jain
2026-07-10 12:27 ` David Hildenbrand (Arm)
2026-07-10 13:13 ` Dev Jain
2026-07-11 0:35 ` Andrew Morton
2026-07-11 12:14 ` Dev Jain [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=7b21094b-fb68-4cb2-8df6-30f6b6dcf0c3@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=harry@kernel.org \
--cc=jannh@google.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=vbabka@kernel.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