From: "Theodore Ts'o" <tytso@mit.edu>
To: Baokun Li <libaokun1@huawei.com>
Cc: "Pankaj Raghav (Samsung)" <kernel@pankajraghav.com>,
Jan Kara <jack@suse.cz>, Luis Chamberlain <mcgrof@kernel.org>,
Pankaj Raghav <p.raghav@samsung.com>,
linux-ext4@vger.kernel.org, Zhang Yi <yi.zhang@huaweicloud.com>
Subject: Re: LBS support for EXT4
Date: Wed, 25 Jun 2025 08:39:03 -0400 [thread overview]
Message-ID: <20250625123903.GB28249@mit.edu> (raw)
In-Reply-To: <dfad7391-e3fe-498d-8d33-55c00d8a3f46@huawei.com>
On Wed, Jun 25, 2025 at 07:51:56PM +0800, Baokun Li wrote:
> Now that mainline ext4 supports buffer head large folios, we'll first
> focus on LBS support based on buffer heads. The main work involves adapting
> ext4's internal logic (e.g., block allocation, read/write operations,
> defragmentation) and clean up the process related to buffer head.
That makes sense; ext4 uses buffer heads for metadata blocks, and so
even if we were using the buffered iomap code, that only is relevant
to the data path, so the changes so that jbd2 and ext4 can suport
large blocks while updating inode table blocks, allocation bitmaps,
etc. would be needed anyway.
Cheers,
- Ted
next prev parent reply other threads:[~2025-06-25 12:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6ac7ce67-b54b-437e-9409-7da9402c9de1@pankajraghav.com>
2025-06-20 15:55 ` LBS support for EXT4 Jan Kara
2025-06-21 0:25 ` Baokun Li
2025-06-21 2:54 ` Zhang Yi
2025-06-23 13:22 ` Pankaj Raghav
2025-06-23 13:14 ` Pankaj Raghav
2025-06-23 14:17 ` Theodore Ts'o
2025-06-25 11:13 ` Pankaj Raghav (Samsung)
2025-06-25 11:51 ` Baokun Li
2025-06-25 12:25 ` Pankaj Raghav (Samsung)
2025-06-25 12:39 ` Theodore Ts'o [this message]
[not found] <c0ea5334-6439-4ec9-a1eb-a9eb0863c3b7@pankajraghav.com>
2025-10-09 8:07 ` LBS support for ext4 Zhang Yi
2025-10-09 8:38 ` Pankaj Raghav
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=20250625123903.GB28249@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--cc=kernel@pankajraghav.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=p.raghav@samsung.com \
--cc=yi.zhang@huaweicloud.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.