linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Miao Xie <miaox@cn.fujitsu.com>
To: Ilya Dryomov <idryomov@gmail.com>,
	Linux Btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH V3 1/2] Btrfs: cleanup duplicated division functions
Date: Thu, 27 Sep 2012 18:15:34 +0800	[thread overview]
Message-ID: <50642746.3050902@cn.fujitsu.com> (raw)
In-Reply-To: <20120924164742.GN14582@twin.jikos.cz>

Sorry to reply late.

On Mon, 24 Sep 2012 18:47:42 +0200, David Sterba wrote:
>>> This is the most straightforward transformation I can think of.  It
>>> doesn't result in an unnecessary BUG_ON, keeps churn to a minimum and
>>
>> agree with you.
>>
>>> doesn't change the "style" of the balance ioctl.  (If I were to check
>>> every filter argument that way, btrfs_balance_ioctl() would be very long
>>> and complicated.)
>>
>> I think the check in btrfs_balance_ioctl() is necessary, the reason is above.
> 
> btrfs_balance_ioctl does not seem as the right place, it does the
> processing related to the state of balance (resume/cancel etc). Look at
> btrfs_balance() itself, it does lot more sanity checks of the parameters

I think we should not put the check in btrfs_balance(), because the arguments
are valid forever if they pass the check when they are input, if we put the
check in btrfs_balance(), the check will be done every time we resume the balance.
it is unnecessary.

> We can put the extra checks into helpers (and not only this
> one) if clarity and readability of the function becomes a concern.

Agree. I will put this check into a helper in the next version of this patch.
And I will make a separate patch to move the current check in btrfs_balance
from btrfs_balance to the above helper after this patch is received.

Thanks
Miao

  parent reply	other threads:[~2012-09-27 10:46 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
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 [this message]
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=50642746.3050902@cn.fujitsu.com \
    --to=miaox@cn.fujitsu.com \
    --cc=idryomov@gmail.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 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).