From: Andreas Dilger <adilger@clusterfs.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: ext3_group_sparse slow?
Date: Wed, 12 Jan 2005 11:23:49 -0700 [thread overview]
Message-ID: <20050112182349.GP8098@schnapps.adilger.int> (raw)
In-Reply-To: <20050112141841.GB25517@atrey.karlin.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 2853 bytes --]
On Jan 12, 2005 15:18 +0100, Jan Kara wrote:
> > On Jan 11, 2005 15:48 +0100, Jan Kara wrote:
> > > I've been profiling dbench load on ext3 on my laptop and it looks as
> > > follows:
> > > CPU: CPU with timer interrupt, speed 0 MHz (estimated)
> > > Profiling through timer interrupt
> > > samples % symbol name
> > > 6540 1.5141 ext3_group_sparse
> > > 3615 0.8369 ext3_get_group_desc
> >
> > The ext3_get_group_desc() code is using a div and mod, which may be
> > what is slowing things down there. These could easily be changed to
> > shift and mask. The ext3_group_desc struct is an on-disk struct and isn't
> > changing size any time soon (ever?) and is also a power of two in size.
> > We already even have s_desc_per_block_bits... Totally untested patch:
> >
> > --- 1.27/fs/ext3/balloc.c 2004-11-11 01:34:33 -07:00
> > +++ edited/fs/ext3/balloc.c 2005-01-11 11:04:55 -07:00
> > @@ -56,8 +56,8 @@
> > }
> > smp_rmb();
> >
> > - group_desc = block_group / EXT3_DESC_PER_BLOCK(sb);
> > - desc = block_group % EXT3_DESC_PER_BLOCK(sb);
> > + group_desc = block_group >> EXT3_DESC_PER_BLOCK_BITS(sb);
> > + desc = block_group & (EXT3_DESC_PER_BLOCK(sb) - 1);
> > if (!EXT3_SB(sb)->s_group_desc[group_desc]) {
> > ext3_error (sb, "ext3_get_group_desc",
> > "Group descriptor not loaded - "
> This looks OK.
>
> > > ext3_group_sparse()
> >
> > As for ext3_group_sparse() this code is very inefficient for large
> > filesystems as it repeatedly does div and mod operations. Far better
> > is to use an incremental method using multiplies
>
> I agree with the idea but would not be the following solution better?
> It's simplier, you save the function call etc..
>
> --- linux-2.6.10.orig/fs/ext3/balloc.c 2005-01-05 17:19:33.000000000 +0100
> +++ linux-2.6.10-ext3speedup/fs/ext3/balloc.c 2005-01-12 13:07:48.000000000 +0100
> @@ -1435,19 +1435,17 @@
>
> static inline int test_root(int a, int b)
> {
> - if (a == 0)
> - return 1;
> - while (1) {
> - if (a == 1)
> - return 1;
> - if (a % b)
> - return 0;
> - a = a / b;
> - }
> + int num = b;
> +
> + while (a > num)
> + num *= b;
> + return num == a;
> }
>
> int ext3_group_sparse(int group)
> {
> + if (group <= 1)
> + return 1;
> return (test_root(group, 3) || test_root(group, 5) ||
> test_root(group, 7));
> }
>
> I profiled your first patch + the above one and ext3_group_sparse()
> takes now 0.27% and ext3_get_group_desc() 0.33% which seems much better
> :) If you agree I can submit it to Andrew.
Sure, you can add my Signed-off-by: Andreas Dilger <adilger@clusterfs.com>
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://members.shaw.ca/adilger/ http://members.shaw.ca/golinux/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-01-12 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-11 14:48 ext3_group_sparse slow? Jan Kara
2005-01-11 18:37 ` Andreas Dilger
2005-01-12 14:18 ` Jan Kara
2005-01-12 18:23 ` Andreas Dilger [this message]
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=20050112182349.GP8098@schnapps.adilger.int \
--to=adilger@clusterfs.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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).