From: Christoph Hellwig <hch@infradead.org>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
brauner@kernel.org, djwong@kernel.org, bfoster@redhat.com,
linux-fsdevel@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v1 6/9] iomap: optimize reads for non-block-aligned writes
Date: Mon, 13 Oct 2025 21:14:28 -0700 [thread overview]
Message-ID: <aO3OJBJL1Y64KJTL@infradead.org> (raw)
In-Reply-To: <CAJnrk1aS9ko2ZxKM0zKm6Uy1zP6RFm6JWJ9Ku2zLSK9LmC4pOg@mail.gmail.com>
On Mon, Oct 13, 2025 at 05:04:30PM -0700, Joanne Koong wrote:
> Ahh okay, that makes sense. I'll drop this patch then.
If this is a big enough win for fuse / network file systems we can
find a way to opt into this behavior.
next prev parent reply other threads:[~2025-10-14 4:14 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 22:56 [PATCH v1 0/9] iomap: buffered io changes Joanne Koong
2025-10-09 22:56 ` [PATCH v1 1/9] iomap: account for unaligned end offsets when truncating read range Joanne Koong
2025-10-13 3:00 ` Christoph Hellwig
2025-10-15 17:34 ` Joanne Koong
2025-10-15 17:40 ` Gao Xiang
2025-10-15 17:49 ` Joanne Koong
2025-10-15 18:06 ` Gao Xiang
2025-10-15 18:21 ` Joanne Koong
2025-10-15 18:39 ` Gao Xiang
2025-10-16 0:36 ` Joanne Koong
2025-10-16 1:27 ` Joanne Koong
2025-10-16 1:58 ` Gao Xiang
2025-10-16 22:03 ` Joanne Koong
2025-10-17 0:03 ` Gao Xiang
2025-10-17 18:41 ` Joanne Koong
2025-10-17 22:07 ` Gao Xiang
2025-10-17 23:22 ` Joanne Koong
2025-10-18 0:12 ` Gao Xiang
2025-10-20 23:25 ` Joanne Koong
2025-10-21 1:39 ` Gao Xiang
2025-10-16 11:29 ` Brian Foster
2025-10-16 22:39 ` Joanne Koong
2025-10-17 15:33 ` Brian Foster
2025-10-17 18:27 ` Brian Foster
2025-10-17 20:19 ` Joanne Koong
2025-10-18 10:30 ` Brian Foster
2025-10-20 21:39 ` Joanne Koong
2025-10-15 18:28 ` Gao Xiang
2025-10-09 22:56 ` [PATCH v1 2/9] docs: document iomap writeback's iomap_finish_folio_write() requirement Joanne Koong
2025-10-13 3:01 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 3/9] iomap: optimize pending async writeback accounting Joanne Koong
2025-10-13 3:04 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 4/9] iomap: simplify ->read_folio_range() error handling for reads Joanne Koong
2025-10-13 3:06 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 5/9] iomap: simplify when reads can be skipped for writes Joanne Koong
2025-10-13 3:06 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 6/9] iomap: optimize reads for non-block-aligned writes Joanne Koong
2025-10-13 3:08 ` Christoph Hellwig
2025-10-14 0:04 ` Joanne Koong
2025-10-14 4:14 ` Christoph Hellwig [this message]
2025-10-09 22:56 ` [PATCH v1 7/9] iomap: use loff_t for file positions and offsets in writeback code Joanne Koong
2025-10-13 3:09 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 8/9] iomap: use find_next_bit() for dirty bitmap scanning Joanne Koong
2025-10-13 3:13 ` Christoph Hellwig
2025-10-09 22:56 ` [PATCH v1 9/9] iomap: use find_next_bit() for uptodate " Joanne Koong
2025-10-13 3:13 ` Christoph Hellwig
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=aO3OJBJL1Y64KJTL@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=joannelkoong@gmail.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.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;
as well as URLs for NNTP newsgroup(s).