From: Heming Zhao <heming.zhao@suse.com>
To: Christoph Hellwig <hch@lst.de>
Cc: joseph.qi@linux.alibaba.com, mark@fasheh.com, jlbec@evilplan.org,
ocfs2-devel@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v5 0/4] migrates ocfs2 DIO from buffer_head to iomap
Date: Fri, 6 Nov 2026 22:09:47 +0800 [thread overview]
Message-ID: <3f975e52-ae09-4f5c-96a5-10629577ce04@suse.com> (raw)
In-Reply-To: <20261106104617.GA5746@lst.de>
On 11/6/26 18:46, Christoph Hellwig wrote:
> s/migrates/migrate/ I think.
>
> On Thu, Nov 05, 2026 at 03:19:24PM +0800, Heming Zhao wrote:
>> To simplify iomap development, we currently adopt the simplest approach:
>> retaining the buffer_head style, where only one cluster is allocated
>> per iomap_begin() call.
>
> Do you mean you'd otherwise need changes to the core iomap code?
> Or do I misunderstand the sentence.
>
Apologies for my English.
"To simplify iomap development" should be "To simplify ocfs2 iomap development".
Because the ocfs2 buffer_head path uses "struct ocfs2_dio_write_ctxt *dwc"
to pass dio unwritten info from the dio get_block phase (ocfs2_dio_wr_get_block())
to the end_io phase (ocfs2_dio_end_io_write()).
However, iomap clears iocb->private before the iomap_dio_ops end_io callback,
which makes it impossible to reuse the current ocfs2 buffer_head end_io function.
- Heming
prev parent reply other threads:[~2026-11-06 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 7:19 Heming Zhao
2026-11-05 7:19 ` [RFC PATCH v5 1/4] ocfs2: Add new ocfs2_map_blocks() to introduce iomap feature Heming Zhao
2026-11-05 7:19 ` [RFC PATCH v5 2/4] ocfs2: switch DIO read path from buffer_head to iomap Heming Zhao
2026-11-06 10:48 ` Christoph Hellwig
2026-11-06 14:11 ` Heming Zhao
2026-11-05 7:19 ` [RFC PATCH v5 3/4] ocfs2: switch dio write " Heming Zhao
2026-11-06 10:52 ` Christoph Hellwig
2026-11-06 14:25 ` Heming Zhao
2026-11-05 7:19 ` [RFC PATCH v5 4/4] ocfs2: remove legacy blockdev direct-IO path APIs Heming Zhao
2026-11-06 10:46 ` [RFC PATCH v5 0/4] migrates ocfs2 DIO from buffer_head to iomap Christoph Hellwig
2026-11-06 14:09 ` Heming Zhao [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=3f975e52-ae09-4f5c-96a5-10629577ce04@suse.com \
--to=heming.zhao@suse.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@lists.linux.dev \
/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
all inboxes | Powered by JetHome®