public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@redhat.com>
To: Eric Sandeen <sandeen@redhat.com>,
	ext4 development <linux-ext4@vger.kernel.org>,
	Alex Tomas <alex@clusterfs.com>
Subject: Re: [PATCH] UPDATED: types fixup for mballoc
Date: Thu, 03 Jan 2008 13:24:40 -0600	[thread overview]
Message-ID: <477D3678.7020203@redhat.com> (raw)
In-Reply-To: <20080103191733.GJ3351@webber.adilger.int>

Andreas Dilger wrote:
> On Jan 02, 2008  14:01 -0600, Eric Sandeen wrote:
>> This patch:
>>
>> changes fe_len to an int, I don't think we need it to be a long,
>> looking at how it's used (should it be a grpblk_t?)  Also change
>> anything assigned to return value of mb_find_extent, since it returns
>> fe_len.
>>
>> changes anything that does groupno * EXT4_BLOCKS_PER_GROUP
>> or pa->pa_pstart + <whatever> to an ext4_fsblk_t
>>
>> fixes up any related formats
>>
>> The change to ext4_mb_scan_aligned to avoid a 64-bit modulo
>> could use an extra look I think.
>>
>> @@ -1732,17 +1735,18 @@ static void ext4_mb_scan_aligned(struct 
>>  	BUG_ON(sbi->s_stripe == 0);
>>  
>> -	/* find first stripe-aligned block */
>> -	i = e4b->bd_group * EXT4_BLOCKS_PER_GROUP(sb)
>> -		+ le32_to_cpu(sbi->s_es->s_first_data_block);
>> -	i = ((i + sbi->s_stripe - 1) / sbi->s_stripe) * sbi->s_stripe;
>> -	i = (i - le32_to_cpu(sbi->s_es->s_first_data_block))
>> -			% EXT4_BLOCKS_PER_GROUP(sb);
> 
>> +	/* find first stripe-aligned block in group */
>> +	a = e4b->bd_group * EXT4_BLOCKS_PER_GROUP(sb)
>> +		+ le32_to_cpu(sbi->s_es->s_first_data_block);
>> +	a = (a + sbi->s_stripe - 1) & ~((ext4_fsblk_t)sbi->s_stripe - 1);
>> +	a = a - le32_to_cpu(sbi->s_es->s_first_data_block);
>> +	i = do_div(a, EXT4_BLOCKS_PER_GROUP(sb));
> 
> I don't think this is correct...  This code should only be used if s_stripe
> is NOT a power-of-two value, otherwise we can just use the buddy maps to
> find aligned chunks.  As a result I don't think that "& (s_stripe - 1)"
> change is equivalent to "/ s_stripe * s_stripe".

Hmmm ok let me re-check that then.

(...curses 64-bit math trickiness...)

>>  	while (i < sb->s_blocksize * 8) {
>>  		if (!mb_test_bit(i, bitmap)) {
> 
> Hrmmm, I thought this should be "while (i < EXT4_BLOCKS_PER_GROUP(sb))"
> and not "sb->s_blocksize * 8"?  Did that fix get lost somewhere?

I did wonder about that.... wondered about the magic 8 number but forgot
to comment.

Thanks,
-Eric

  reply	other threads:[~2008-01-03 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15 22:56 [PATCH] types fixup for mballoc Eric Sandeen
2007-11-16  4:49 ` Eric Sandeen
2008-01-02 20:01   ` [PATCH] UPDATED: " Eric Sandeen
2008-01-03 19:17     ` Andreas Dilger
2008-01-03 19:24       ` Eric Sandeen [this message]
2008-01-03 20:10         ` [PATCH] UPDATED2: " Eric Sandeen
2008-01-03 20:35           ` Andreas Dilger
2008-01-03 21:07             ` Eric Sandeen
2008-01-08 19:54           ` [PATCH] UPDATED3: " Eric Sandeen
2008-01-09  3:47             ` Andreas Dilger

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=477D3678.7020203@redhat.com \
    --to=sandeen@redhat.com \
    --cc=alex@clusterfs.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