From: Allison Henderson <achender@vnet.ibm.com>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: PATCH 0/2 v2] EXT4: Punch Hole Optimizations
Date: Mon, 06 Jun 2011 16:43:37 -0700 [thread overview]
Message-ID: <4DED6629.3010403@vnet.ibm.com> (raw)
Hi all,
We realized late that we could optimize the punch hole code by skipping
ext4_ext_remove_space, and directly calling ext4_ext_rm_leaf. Since
punch hole is done through map blocks, the path to the extent is already
known, so we do not need to look it up again. The extra parameter that
was added in ext4_ext_remove_space is removed since we no longer need it.
Allison Henderson
reply other threads:[~2011-06-06 23:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4DED6629.3010403@vnet.ibm.com \
--to=achender@vnet.ibm.com \
--cc=linux-ext4@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).