From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/3] Optimize __ext4_block_zero_page_range() for unwritten buffers
Date: Fri, 29 Sep 2023 19:40:42 +0530 [thread overview]
Message-ID: <cover.1695987265.git.ojaswin@linux.ibm.com> (raw)
As per discussion with Jan here [1], this patchset intends to exit early
from __ext4_block_zero_page_range() incase the block we are about to
zero (partially) is unwritten and unmapped, since such a block doesn't
require zeroing.
Further, also make sure that calls to ext4_zero_partial_blocks()
truncate the page cache completely beforehand, so that they don't rely
on ext4_zero_partial_block() -> __ext4_block_zero_page_range() to zero
out non block aligned edges of pagecache.
Reviews and comments are appreciated!
Regards,
ojaswin
[1]
https://lore.kernel.org/linux-ext4/20230914141920.lw2nlpzhcxwuz2y6@quack3/
Ojaswin Mujoo (3):
ext4: treat end of range as exclusive in ext4_zero_range()
ext4: truncate complete range in pagecache before calling
ext4_zero_partial_blocks()
ext4: Skip unwritten buffers in __ext4_block_zero_page_range()
fs/ext4/extents.c | 20 +++++++++++++-------
fs/ext4/inode.c | 7 +++++--
2 files changed, 18 insertions(+), 9 deletions(-)
--
2.39.3
next reply other threads:[~2023-09-29 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-29 14:10 Ojaswin Mujoo [this message]
2023-09-29 14:10 ` [PATCH 1/3] ext4: treat end of range as exclusive in ext4_zero_range() Ojaswin Mujoo
2023-10-19 15:01 ` Jan Kara
2023-09-29 14:10 ` [PATCH 2/3] ext4: truncate complete range in pagecache before calling ext4_zero_partial_blocks() Ojaswin Mujoo
2023-09-29 16:15 ` Ojaswin Mujoo
2023-10-19 16:55 ` Jan Kara
2023-11-01 15:45 ` Ojaswin Mujoo
2023-09-29 14:10 ` [PATCH 3/3] ext4: Skip unwritten buffers in __ext4_block_zero_page_range() Ojaswin Mujoo
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=cover.1695987265.git.ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
/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).