From: Christoph Hellwig <hch@infradead.org>
To: Salvatore Dipietro <dipiets@amazon.it>
Cc: hch@infradead.org, ritesh.list@gmail.com, abuehaze@amazon.com,
akpm@linux-foundation.org, alisaidi@amazon.com,
blakgeof@amazon.com, brauner@kernel.org, david@kernel.org,
dipietro.salvatore@gmail.com, 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: Mon, 6 Jul 2026 23:22:38 -0700 [thread overview]
Message-ID: <akybLlAsw7Yv1Xmb@infradead.org> (raw)
In-Reply-To: <aj0bDijqj1-Bjxq1@infradead.org>
On Thu, Jun 25, 2026 at 05:11:58AM -0700, Christoph Hellwig wrote:
> On Thu, Jun 25, 2026 at 09:10:37AM +0000, Salvatore Dipietro wrote:
> > 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]
>
> The page_alloc.c change definitively seems like the right thing to do from
> the high-level POV. It would also be nice to find a way to centralize
> the logic for which flags to set in a central place as we have quite a
> few other places that want to allocate large folios optimistically.
Can you submit a formal patch for this? I.e. proper commit log,
fixes tag, separate thread, etc.
next prev parent reply other threads:[~2026-07-07 6:22 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
2026-06-25 12:11 ` Christoph Hellwig
2026-07-07 6:22 ` Christoph Hellwig [this message]
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=akybLlAsw7Yv1Xmb@infradead.org \
--to=hch@infradead.org \
--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=dipiets@amazon.it \
--cc=djwong@kernel.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