From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Christoph Hellwig <hch@infradead.org>, Pedro Falcato <pfalcato@suse.de>
Cc: Kiryl Shutsemau <kas@kernel.org>,
Lance Yang <lance.yang@linux.dev>,
usama.arif@linux.dev, hughd@google.com,
akpm@linux-foundation.org, baohua@kernel.org,
baolin.wang@linux.alibaba.com, dev.jain@arm.com,
liam@infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ljs@kernel.org, nico.pache@linux.dev,
ryan.roberts@arm.com, ziy@nvidia.com, nphamcs@gmail.com,
hannes@cmpxchg.org, riel@surriel.com, shakeel.butt@linux.dev,
kernel-team@meta.com, stable@vger.kernel.org,
willy@infradead.org
Subject: Re: [PATCH] mm/huge_memory: transfer the pmd dirty bit to the folio on zap
Date: Tue, 25 Aug 2026 10:04:31 +0200 [thread overview]
Message-ID: <2614286d-19ed-4848-8ce6-59ebecf19d1d@kernel.org> (raw)
In-Reply-To: <ao0vSde26_Qar0IZ@infradead.org>
On 8/25/26 07:59, Christoph Hellwig wrote:
> On Thu, Aug 20, 2026 at 03:10:11PM +0100, Pedro Falcato wrote:
>>> Why? Write batching from large folios is a win.
>>
>> For some context: we were discussing (off-list) the recent report that
>> systemd-journald had horrible write amplification, worsed quite a bit
>> by large folios. At the moment, there is quite a lot of write amplification,
>> but _only_ on mmap writes (if you look at the write(2) paths, you'll see
>> write_begin and write_end which tactically only dirty what you actually wrote
>> to, block-wise in the BHs or iomap IFS). This doesn't need to be true.
>
> So don't use mmap to write to storage. That is always a bad idea for
> many, many reasons. We should not work around broken applications that
> do this, but change them. It only took about 10 years of bad reputation
> for MongoDB to finally fix their act, so it should be possible for
> systemd as well.
I was in contact with systemd folks (and pulled in Willy and Jan) regarding
that, and nothing should really block that.
--
Cheers,
David
next prev parent reply other threads:[~2026-08-25 8:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 10:12 [PATCH] mm/huge_memory: transfer the pmd dirty bit to the folio on zap Usama Arif
2026-08-19 14:13 ` David Hildenbrand (Arm)
2026-08-19 14:13 ` David Hildenbrand (Arm)
2026-08-19 14:31 ` Kiryl Shutsemau
2026-08-19 16:17 ` Lance Yang
2026-08-19 16:32 ` Usama Arif
2026-08-20 13:05 ` Usama Arif
2026-08-19 16:35 ` Pedro Falcato
2026-08-20 6:13 ` Lance Yang
2026-08-20 12:12 ` Pedro Falcato
2026-08-20 13:20 ` Kiryl Shutsemau
2026-08-20 14:10 ` Pedro Falcato
2026-08-20 16:53 ` Lance Yang
2026-08-20 22:20 ` Pedro Falcato
2026-08-25 5:59 ` Christoph Hellwig
2026-08-25 8:04 ` David Hildenbrand (Arm) [this message]
2026-08-25 8:40 ` Pedro Falcato
2026-08-26 4:42 ` Christoph Hellwig
2026-08-25 5:57 ` Christoph Hellwig
2026-08-19 20:33 ` Hugh Dickins
2026-08-19 15:10 ` Lance Yang
2026-08-19 15:31 ` Zi Yan
2026-08-19 16:09 ` Lorenzo Stoakes (ARM)
2026-08-20 2:06 ` Baolin Wang
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=2614286d-19ed-4848-8ce6-59ebecf19d1d@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=kas@kernel.org \
--cc=kernel-team@meta.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=nico.pache@linux.dev \
--cc=nphamcs@gmail.com \
--cc=pfalcato@suse.de \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.com \
--cc=shakeel.butt@linux.dev \
--cc=stable@vger.kernel.org \
--cc=usama.arif@linux.dev \
--cc=willy@infradead.org \
--cc=ziy@nvidia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox