From: "Lukáš Czerner" <lczerner@redhat.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH 1/6 -v2] libext2fs: optimize rb_set_bmap_range()
Date: Tue, 27 Nov 2012 08:16:15 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1211270815380.8846@localhost> (raw)
In-Reply-To: <1353947981-15219-2-git-send-email-tytso@mit.edu>
On Mon, 26 Nov 2012, Theodore Ts'o wrote:
> Date: Mon, 26 Nov 2012 11:39:35 -0500
> From: Theodore Ts'o <tytso@mit.edu>
> To: Ext4 Developers List <linux-ext4@vger.kernel.org>
> Cc: Theodore Ts'o <tytso@mit.edu>
> Subject: [PATCH 1/6 -v2] libext2fs: optimize rb_set_bmap_range()
>
> This speeds up reading bitmaps from disk for very large (and full)
> disks by significant amounts (i.e., up to two CPU minutes for a 4T
> file system).
>
> Addresses-Google-Bug: #7534813
Looks good.
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
> lib/ext2fs/blkmap64_rb.c | 32 +++++++++++++++++++++++++++++---
> 1 file changed, 29 insertions(+), 3 deletions(-)
>
> diff --git a/lib/ext2fs/blkmap64_rb.c b/lib/ext2fs/blkmap64_rb.c
> index a42eda1..0fc7c57 100644
> --- a/lib/ext2fs/blkmap64_rb.c
> +++ b/lib/ext2fs/blkmap64_rb.c
> @@ -674,16 +674,42 @@ static errcode_t rb_set_bmap_range(ext2fs_generic_bitmap bitmap,
> __u64 start, size_t num, void *in)
> {
> struct ext2fs_rb_private *bp;
> + unsigned char *cp = in;
> size_t i;
> + int first_set = -1;
> int ret;
>
> bp = (struct ext2fs_rb_private *) bitmap->private;
>
> for (i = 0; i < num; i++) {
> - ret = ext2fs_test_bit(i, in);
> - if (ret)
> - rb_insert_extent(start + i - bitmap->start, 1, bp);
> + if (i & 7 == 0) {
> + unsigned char c = cp[i/8];
> + if (c == 0xFF) {
> + if (first_set == -1)
> + first_set = i;
> + i += 7;
> + continue;
> + }
> + if ((c == 0x00) && (first_set == -1)) {
> + i += 7;
> + continue;
> + }
> + }
> + if (ext2fs_test_bit(i, in)) {
> + if (first_set == -1)
> + first_set = i;
> + continue;
> + }
> + if (first_set == -1)
> + continue;
> +
> + rb_insert_extent(start + first_set - bitmap->start,
> + i - first_set, bp);
> + first_set = -1;
> }
> + if (first_set != -1)
> + rb_insert_extent(start + first_set - bitmap->start,
> + num - first_set, bp);
>
> return 0;
> }
>
next prev parent reply other threads:[~2012-11-27 7:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 16:39 [PATCH 0/6 -v2] Optimize e2fsck for large file systems Theodore Ts'o
2012-11-26 16:39 ` [PATCH 1/6 -v2] libext2fs: optimize rb_set_bmap_range() Theodore Ts'o
2012-11-27 7:16 ` Lukáš Czerner [this message]
2012-11-26 16:39 ` [PATCH 2/6 -v2] e2fsck: optimize pass1 for CPU time Theodore Ts'o
2012-11-26 16:39 ` [PATCH 3/6 -v3] libext2fs: add ext2fs_bitcount() function Theodore Ts'o
2012-11-26 23:17 ` Zach Brown
2012-11-27 1:45 ` Theodore Ts'o
2012-11-27 5:16 ` Theodore Ts'o
2012-11-27 17:50 ` Zach Brown
2012-11-27 19:37 ` Theodore Ts'o
2012-11-27 17:54 ` Zach Brown
2012-11-26 16:39 ` [PATCH 4/6 -v2] libext2fs: optimize rb_get_bmap_range() Theodore Ts'o
2012-11-26 16:39 ` [PATCH 5/6 -v2] libext2fs: optimize rb_get_bmap_range() for mostly allocated bmaps Theodore Ts'o
2012-11-26 16:39 ` [PATCH 6/6 -v2] e2fsck: optimize pass 5 for CPU utilization Theodore Ts'o
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=alpine.LFD.2.00.1211270815380.8846@localhost \
--to=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--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).