All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] Btrfs: cleanup duplicated division functions
Date: Fri, 21 Sep 2012 16:26:31 +0800	[thread overview]
Message-ID: <505C24B7.5080508@cn.fujitsu.com> (raw)
In-Reply-To: <20120920132802.GM17430@twin.jikos.cz>

On Thu, 20 Sep 2012 15:28:03 +0200, David Sterba wrote:
> On Thu, Sep 20, 2012 at 10:57:54AM +0800, Miao Xie wrote:
>> Because those functions are mostly used on the hot path, and we are sure
>> the parameters are right in the most cases, we don't add complex checks
>> for the parameters. But in the other place, we must check and make sure
>> the parameters are right. So besides the code cleanup, this patch also
>> add a check for the usage of the space balance, it is the only place that
>> we need add check to make sure the parameters of div_factor{_fine} are
>> right till now.
> 
> I've reviewed the hotpaths, makes sense to optimize for speed. Adding
> the boundary checks to balance ioctl is ok.
> 
> A few suggestions:
> 
> * drop the version that does the /10 version and keep only /100 (naming
>   it div_factor)
> * drop the
> 
> +	if (factor == 10)
> +		return num;
> 
> check, there's only one instance where we pass the maximum value (and
> it's not a frequent case), so there's the if() penalty, makes the
> function smaller and even more suitable for inlining.

OK.

> 
>> diff --git a/fs/btrfs/ioctl.c b/fs/btrfs/ioctl.c
>> index 9384a2a..d8d53f7 100644
>> --- a/fs/btrfs/ioctl.c
>> +++ b/fs/btrfs/ioctl.c
>> @@ -3335,6 +3335,24 @@ static long btrfs_ioctl_balance(struct file *file, void __user *arg)
>>  
>>  			goto do_balance;
>>  		}
>> +
>> +		if ((bargs->data.flags & BTRFS_BALANCE_ARGS_USAGE) &&
>> +		    (bargs->data.usage < 0 || bargs->data.usage > 100)) {
> 
> data.usage <= 0
> 
> otherwise you'd divide by 0 in chunk_usage_filter()

The divisor always is 100 or 10, so...

>> diff --git a/fs/btrfs/math.h b/fs/btrfs/math.h
>> new file mode 100644
>> index 0000000..b7816ce
>> --- /dev/null
>> +++ b/fs/btrfs/math.h
> 
> I think we don't need single file to hold one trivial function then :)
> 
>> @@ -0,0 +1,44 @@
>> +#include <asm/div64.h>
>> +
>> +static inline u64 div_factor(u64 num, int factor)
>> +{
>> +	num *= factor;
>> +	do_div(num, 100);
>> +	return num;
>> +}

I don't find a suitable file to put it down. Maybe we can stuff it
into ctree.h, but I prefer a single file to a unrelated file.

Thanks
Miao

  reply	other threads:[~2012-09-21  8:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 10:51 [PATCH 1/2] Btrfs: cleanup duplicated division functions Miao Xie
2012-09-14 13:54 ` David Sterba
2012-09-17  2:21   ` Miao Xie
2012-09-17 12:07     ` Ilya Dryomov
2012-09-17 16:31     ` David Sterba
2012-09-18  3:53       ` Miao Xie
2012-09-20  2:57 ` [PATCH V2 " Miao Xie
2012-09-20 13:28   ` David Sterba
2012-09-21  8:26     ` Miao Xie [this message]
2012-09-21  9:07   ` [PATCH V3 " Miao Xie
2012-09-21 15:24     ` David Sterba
2012-09-23  9:54       ` Miao Xie
2012-09-24 16:33         ` David Sterba
2012-09-23 11:49     ` Ilya Dryomov
2012-09-24  2:05       ` Miao Xie
2012-09-24 16:47         ` David Sterba
2012-09-24 18:42           ` Ilya Dryomov
2012-09-25 10:24             ` Miao Xie
2012-09-27 10:15           ` Miao Xie
2012-09-27 10:19     ` [PATCH V4 " Miao Xie
2012-09-27 16:56       ` Ilya Dryomov
2012-09-28  1:30         ` Miao Xie
2012-09-28  1:49       ` [PATCH V5 " Miao Xie
2012-09-28 10:09         ` David Sterba

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=505C24B7.5080508@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=linux-btrfs@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 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.