From: Salvatore Dipietro <dipiets@amazon.it>
To: <hch@infradead.org>, <ritesh.list@gmail.com>
Cc: <abuehaze@amazon.com>, <akpm@linux-foundation.org>,
<alisaidi@amazon.com>, <blakgeof@amazon.com>,
<brauner@kernel.org>, <david@kernel.org>,
<dipietro.salvatore@gmail.com>, <dipiets@amazon.it>,
<djwong@kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-xfs@vger.kernel.org>, <ljs@kernel.org>, <mhocko@suse.com>,
<rppt@kernel.org>, <stable@vger.kernel.org>, <vbabka@kernel.org>,
<vbabka@suse.com>, <willy@infradead.org>
Subject: Re: [PATCH 1/1] iomap: avoid compaction for costly folio order allocation
Date: Thu, 25 Jun 2026 09:10:37 +0000 [thread overview]
Message-ID: <20260625091039.24501-1-dipiets@amazon.it> (raw)
In-Reply-To: <ajvc7fSDngyx0X5j@infradead.org>
On Wed, Jun 24, 2026 at 12:21:00PM +0000, Ritesh Harjani wrote:
> Sorry about the delay. I did bring this topic up in one of our internal
> ext4 community calls. And to share some context, MM community thinks we
> need a better long term fix for this problem rather than patching call
> sites and/or playing tricks like -
Thanks Ritesh for the update and for bringing this to the wider MM community.
I completely understand that the MM community is looking for a proper long-term
fix rather than specific patching.
On Wed, Jun 24, 2026 at 13:34:00PM +0000, Christoph Hellwig wrote:
> Do you have ointers to the patches for each approach above?
Yes — all the patches in the result table are shared within this thread:
v1 (original, iomap caller): The original PATCH 1/1 in this series
Ritesh's suggestion (mm/filemap.c): Shared in Ritesh's reply on May 3rd [1]
Matthew's suggestion (mm/filemap.c): Shared in Matthew's reply on April 4th [2]
kcompactd background (mm/page_alloc.c): Shared in my reply on May 6th [3]
[1] https://lore.kernel.org/all/20260403193535.9970-1-dipiets@amazon.it/T/#m8c3da1c9fb9e9c66d4e8b1849de824b0ecf37f9e
[2] https://lore.kernel.org/all/20260403193535.9970-1-dipiets@amazon.it/T/#m4b90cf280ff0efcf178dfd8d068f1de3b262e28a
[3] https://lore.kernel.org/all/20260403193535.9970-1-dipiets@amazon.it/T/#m22977355535a4599084a51104a4df806d49c53d1
--
Salvatore
AMAZON DEVELOPMENT CENTER ITALY SRL, viale Monte Grappa 3/5, 20124 Milano, Italia, Registro delle Imprese di Milano Monza Brianza Lodi REA n. 2504859, Capitale Sociale: 10.000 EUR i.v., Cod. Fisc. e P.IVA 10100050961, Societa con Socio Unico
next prev parent reply other threads:[~2026-06-25 9:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 19:35 [PATCH 0/1] iomap: avoid compaction for costly folio order allocation Salvatore Dipietro
2026-04-03 19:35 ` [PATCH 1/1] " Salvatore Dipietro
2026-04-04 1:13 ` Ritesh Harjani
2026-04-04 4:15 ` Matthew Wilcox
2026-04-04 16:47 ` Ritesh Harjani
2026-04-04 20:46 ` Matthew Wilcox
2026-04-16 15:14 ` Ritesh Harjani
2026-04-20 16:33 ` Salvatore Dipietro
2026-04-20 18:44 ` Matthew Wilcox
2026-04-21 1:16 ` Ritesh Harjani
2026-04-28 15:02 ` Salvatore Dipietro
2026-05-03 5:52 ` Ritesh Harjani
2026-05-03 11:55 ` Matthew Wilcox
2026-05-06 12:33 ` Salvatore Dipietro
2026-05-27 16:24 ` Salvatore Dipietro
2026-05-31 23:29 ` Karim Manaouil
2026-06-05 10:58 ` Salvatore Dipietro
2026-06-24 8:06 ` Salvatore Dipietro
2026-06-24 12:21 ` Ritesh Harjani
2026-06-24 13:34 ` Christoph Hellwig
2026-06-25 9:10 ` Salvatore Dipietro [this message]
2026-06-25 12:11 ` Christoph Hellwig
2026-07-07 6:22 ` Christoph Hellwig
2026-04-05 22:43 ` Dave Chinner
2026-04-07 5:40 ` Christoph Hellwig
2026-04-21 9:02 ` Vlastimil Babka
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=20260625091039.24501-1-dipiets@amazon.it \
--to=dipiets@amazon.it \
--cc=abuehaze@amazon.com \
--cc=akpm@linux-foundation.org \
--cc=alisaidi@amazon.com \
--cc=blakgeof@amazon.com \
--cc=brauner@kernel.org \
--cc=david@kernel.org \
--cc=dipietro.salvatore@gmail.com \
--cc=djwong@kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=ritesh.list@gmail.com \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vbabka@kernel.org \
--cc=vbabka@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox