From: Wang Shilong <wangsl-fnst@cn.fujitsu.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: chris.mason@fusionio.com, linux-btrfs@vger.kernel.org,
Arne Jansen <sensille@gmx.net>
Subject: Re: [PATCH v2 1/3] Btrfs: split btrfs_qgroup_account_ref into four functions
Date: Tue, 16 Apr 2013 17:56:05 +0800 [thread overview]
Message-ID: <516D2035.6010800@cn.fujitsu.com> (raw)
In-Reply-To: <516D1C25.5060103@jan-o-sch.net>
Hello Jan,
> On Tue, April 16, 2013 at 11:20 (+0200), Wang Shilong wrote:
>> Hello Jan,
>>
>>> The function is separated into a preparation part and the three accounting
>>> steps mentioned in the qgroups documentation. The goal is to make steps two
>>> and three usable by the rescan functionality. A side effect is that the
>>> function is restructured into readable subunits.
>>
>> How about renaming the three functions like:
>>
>> 1> qgroup_walk_old_roots()
>> 2> qgroup_walk_new_root()
>> 3> qgroup_rewalk_old_root()
>>
>> I'd like this function to be meaningful, but not just step1,2,3.
>> Maybe you can think out better function name.
>
> I'd like to keep it like 1, 2, 3, because that matches the documentation in the
> qgroup pdf and the code has always been documented in those three steps.
Oh, Yes, i have read the pdf carefully. I think the pdf document it three steps
just to make it clear that we need 3 steps. But static checker may want to know what is 3 steps
just by the function name but not to read the pdf.
In fact the tree steps are just do:
1>walk old roots
2>walk new root
3>rewalk old root
So i think rename the function like these will make things better. ^_^
Thanks,
Wang
>
> Thanks,
> -Jan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2013-04-16 9:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 8:45 [PATCH v2 0/3] Btrfs: quota rescan for 3.10 Jan Schmidt
2013-04-16 8:45 ` [PATCH v2 1/3] Btrfs: split btrfs_qgroup_account_ref into four functions Jan Schmidt
2013-04-16 9:20 ` Wang Shilong
2013-04-16 9:38 ` Jan Schmidt
2013-04-16 9:56 ` Wang Shilong [this message]
2013-04-16 10:32 ` David Sterba
2013-04-16 10:47 ` Wang Shilong
2013-04-16 10:59 ` David Sterba
2013-04-16 8:45 ` [PATCH v2 2/3] Btrfs: rescan for qgroups Jan Schmidt
2013-04-16 9:26 ` Wang Shilong
2013-04-16 9:39 ` Jan Schmidt
2013-04-16 9:48 ` Wang Shilong
2013-04-16 10:08 ` Wang Shilong
2013-04-16 10:34 ` Jan Schmidt
2013-04-16 10:52 ` David Sterba
2013-04-16 12:22 ` Wang Shilong
2013-04-17 15:20 ` Jan Schmidt
2013-04-16 8:45 ` [PATCH v2 3/3] Btrfs: automatic rescan after "quota enable" command Jan Schmidt
2013-04-16 12:55 ` Wang Shilong
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=516D2035.6010800@cn.fujitsu.com \
--to=wangsl-fnst@cn.fujitsu.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
--cc=sensille@gmx.net \
/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