All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH v2 11/18] btrfs: qgroup: Add new qgroup calculation function btrfs_qgroup_account_extents().
Date: Fri, 3 Jul 2015 08:31:56 +0800	[thread overview]
Message-ID: <5595D7FC.60807@cn.fujitsu.com> (raw)
In-Reply-To: <20150702144349.GN726@twin.jikos.cz>



David Sterba wrote on 2015/07/02 16:43 +0200:
> On Wed, Apr 29, 2015 at 10:29:04AM +0800, Qu Wenruo wrote:
>> The new btrfs_qgroup_account_extents() function should be called in
>> btrfs_commit_transaction() and it will update all the qgroup according
>> to delayed_ref_root->dirty_extent_root.
>>
>> The new function can handle both normal operation during
>> commit_transaction() or in rescan in a unified method with clearer
>> logic.
>>
>> Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
>> ---
>> v2:
>>    Also free ulist even quota is disabled to avoid possible memory leak.
>> ---
>>   fs/btrfs/extent-tree.h |   0
>
> Surprise, this adds an empty file. What was the intention?
My fault, it seems I opened the non-existing file and saved it...
Do I need to submit a patch to remove it?

Thanks,
Qu
> --
> 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
>

  reply	other threads:[~2015-07-03  0:31 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29  2:28 [PATCH 00/18] New extent-oriented qgroup mechanism with minor cleanup Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 01/18] btrfs: backref: Don't merge refs which are not for same block Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 02/18] btrfs: delayed-ref: Use list to replace the ref_root in ref_head Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 03/18] btrfs: delayed-ref: Cleanup the unneeded functions Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 04/18] btrfs: qgroup: Cleanup open-coded old/new_refcnt update and read Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 05/18] btrfs: extent-tree: Use ref_node to replace unneeded parameters in __inc_extent_ref() and __free_extent() Qu Wenruo
2015-04-29  2:28 ` [PATCH v2 06/18] btrfs: qgroup: Add function qgroup_update_refcnt() Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 07/18] btrfs: qgroup: Add function qgroup_update_counters() Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 08/18] btrfs: qgroup: Record possible quota-related extent for qgroup Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 09/18] btrfs: qgroup: Add new function to record old_roots Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 10/18] btrfs: backref: Add special time_seq == (u64)-1 case for btrfs_find_all_roots() Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 11/18] btrfs: qgroup: Add new qgroup calculation function btrfs_qgroup_account_extents() Qu Wenruo
2015-07-02 14:43   ` David Sterba
2015-07-03  0:31     ` Qu Wenruo [this message]
2015-07-03  8:55       ` David Sterba
2015-04-29  2:29 ` [PATCH v2 12/18] btrfs: qgroup: Switch rescan to new mechanism Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 13/18] btrfs: qgroup: Switch to new extent-oriented qgroup mechanism Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 14/18] btrfs: qgroup: Switch self test to " Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 15/18] btrfs: qgroup: Cleanup the old ref_node-oriented mechanism Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 16/18] btrfs: ulist: Add ulist_del() function Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 17/18] btrfs: qgroup: Add the ability to skip given qgroup for old/new_roots Qu Wenruo
2015-04-29  2:29 ` [PATCH v2 18/18] btrfs: qgroup: Make snapshot accounting work with new extent-oriented qgroup Qu Wenruo

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=5595D7FC.60807@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=dsterba@suse.cz \
    --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.