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 4/6] libext2fs: optimize rb_get_bmap_range()
Date: Mon, 26 Nov 2012 11:46:24 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.2.00.1211261146110.18234@localhost> (raw)
In-Reply-To: <1353803794-11593-5-git-send-email-tytso@mit.edu>
On Sat, 24 Nov 2012, Theodore Ts'o wrote:
> Date: Sat, 24 Nov 2012 19:36:32 -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 4/6] libext2fs: optimize rb_get_bmap_range()
>
> This simplifies the rb_get_bmap_range() function and speeds it up for
> the case where most of the bitmap is zero.
Looks good
Reviewed-by: Lukas Czerner <lczerner@redhat.com>
>
> Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
> ---
> lib/ext2fs/blkmap64_rb.c | 25 ++++++++-----------------
> 1 file changed, 8 insertions(+), 17 deletions(-)
>
> diff --git a/lib/ext2fs/blkmap64_rb.c b/lib/ext2fs/blkmap64_rb.c
> index 816f44f..0705cf2 100644
> --- a/lib/ext2fs/blkmap64_rb.c
> +++ b/lib/ext2fs/blkmap64_rb.c
> @@ -741,32 +741,23 @@ static errcode_t rb_get_bmap_range(ext2fs_generic_bitmap bitmap,
> break;
> }
>
> - pos = start;
> + memset(out, 0, (num + 7) >> 3);
> +
> for (; parent != NULL; parent = next) {
> next = ext2fs_rb_next(parent);
> ext = ext2fs_rb_entry(parent, struct bmap_rb_extent, node);
>
> - while (((pos - start) < num) &&
> - (pos < ext->start)) {
> - ext2fs_fast_clear_bit64((pos - start), out);
> - pos++;
> - }
> -
> - if ((pos - start) >= num)
> - return 0;
> + pos = ext->start;
> + if (pos < start)
> + pos = start;
>
> - while (((pos - start) < num) &&
> - (pos < (ext->start + ext->count))) {
> + while (pos < (ext->start + ext->count)) {
> + if ((pos - start) >= num)
> + return 0;
> ext2fs_fast_set_bit64((pos - start), out);
> pos++;
> }
> }
> -
> - while ((pos - start) < num) {
> - ext2fs_fast_clear_bit64((pos - start), out);
> - pos++;
> - }
> -
> return 0;
> }
>
>
next prev parent reply other threads:[~2012-11-26 10:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 0:36 [RFC PATCH 0/6] Optimize e2fsck for large file systems Theodore Ts'o
2012-11-25 0:36 ` [PATCH 1/6] libext2fs: optimize rb_set_bmap_range() Theodore Ts'o
2012-11-26 9:40 ` Lukáš Czerner
2012-11-26 13:36 ` Theodore Ts'o
2012-11-25 0:36 ` [PATCH 2/6] e2fsck: optimize pass1 for CPU time Theodore Ts'o
2012-11-26 10:06 ` Lukáš Czerner
2012-11-25 0:36 ` [PATCH 3/6] libext2fs: add ext2fs_bitcount() function Theodore Ts'o
2012-11-26 10:30 ` Lukáš Czerner
2012-11-26 14:06 ` Theodore Ts'o
2012-11-26 14:10 ` [PATCH 3/6 -v2] " Theodore Ts'o
2012-11-26 14:12 ` [PATCH 4/6 -v3] " Theodore Ts'o
2012-11-25 0:36 ` [PATCH 4/6] libext2fs: optimize rb_get_bmap_range() Theodore Ts'o
2012-11-26 10:46 ` Lukáš Czerner [this message]
2012-11-25 0:36 ` [PATCH 5/6] libext2fs: optimize rb_get_bmap_range() for mostly allocated bmaps Theodore Ts'o
2012-11-26 11:22 ` Lukáš Czerner
2012-11-26 14:17 ` Theodore Ts'o
2012-11-25 0:36 ` [PATCH 6/6] e2fsck: optimize pass 5 for CPU utilization Theodore Ts'o
2012-11-26 11:59 ` Lukáš Czerner
2012-11-25 5:09 ` [RFC PATCH 0/6] Optimize e2fsck for large file systems Theodore Ts'o
2012-11-26 9:19 ` Lukáš Czerner
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.1211261146110.18234@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 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.