From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH RFC 05/14] btrfs: qgroup: Introduce function to reserve data range per inode
Date: Mon, 31 Aug 2015 16:54:36 +0800 [thread overview]
Message-ID: <1441011286-23733-6-git-send-email-quwenruo@cn.fujitsu.com> (raw)
In-Reply-To: <1441011286-23733-1-git-send-email-quwenruo@cn.fujitsu.com>
Introduce new function reserve_data_range().
This function will find non-overlap range and to insert it into reserve
map using previously introduced funtions.
This provides the basis for later per inode reserve map implement.
Signed-off-by: Qu Wenruo <quwenruo@cn.fujitsu.com>
---
fs/btrfs/qgroup.c | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 92 insertions(+)
diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
index 90f5c4b..3948882 100644
--- a/fs/btrfs/qgroup.c
+++ b/fs/btrfs/qgroup.c
@@ -2672,6 +2672,98 @@ static int insert_data_ranges(struct btrfs_qgroup_data_rsv_map *map,
}
/*
+ * Check qgroup limit and insert dirty range into reserve_map.
+ *
+ * Must be called with map->lock hold
+ */
+static int reserve_data_range(struct btrfs_root *root,
+ struct btrfs_qgroup_data_rsv_map *map,
+ struct data_rsv_range *tmp,
+ struct ulist *insert_list, u64 start, u64 len)
+{
+ struct data_rsv_range *range;
+ u64 cur_start = 0;
+ u64 cur_len = 0;
+ u64 reserve = 0;
+ int ret = 0;
+
+ range = find_reserve_range(map, start);
+ /* empty tree, insert the whole range */
+ if (!range) {
+ reserve = len;
+ ret = ulist_add(insert_list, start, len, GFP_ATOMIC);
+ if (ret < 0)
+ return ret;
+ goto insert;
+ }
+
+ /* For case range is covering the leading part */
+ if (range->start <= start && range->start + range->len > start)
+ cur_start = range->start + range->len;
+ else
+ cur_start = start;
+
+ /*
+ * iterate until the end of the range.
+ * Like the following:
+ *
+ * |<--------desired---------------------->|
+ *|//1//| |////2///| |///3///| <- exists
+ * Then we will need to insert the following
+ * |\\\4\\\| |\\\5\\| |\\\6\\\|
+ * And only add qgroup->reserved for rang 4,5,6.
+ */
+ while (cur_start < start + len) {
+ struct rb_node *next_node;
+ u64 next_start;
+
+ if (range->start + range->len <= cur_start) {
+ /*
+ * Move to next range if current range is before
+ * cur_start
+ * e.g range is 1, cur_start is the end of range 1.
+ */
+ next_node = rb_next(&range->node);
+ if (!next_node) {
+ /*
+ * no next range, fill the rest
+ * e.g range is 3, cur_start is end of range 3.
+ */
+ cur_len = start + len - cur_start;
+ next_start = start + len;
+ } else {
+ range = rb_entry(next_node,
+ struct data_rsv_range, node);
+ cur_len = min(range->start, start + len) -
+ cur_start;
+ next_start = range->start + range->len;
+ }
+ } else {
+ /*
+ * current range is already after cur_start
+ * e.g range is 2, cur_start is end of range 1.
+ */
+ cur_len = range->start - cur_len;
+ next_start = range->start + range->len;
+ }
+ reserve += cur_len;
+ ret = ulist_add(insert_list, cur_start, cur_len, GFP_ATOMIC);
+ if (ret < 0)
+ return ret;
+
+ cur_start = next_start;
+ }
+insert:
+ ret = btrfs_qgroup_reserve(root, reserve);
+ if (ret < 0)
+ return ret;
+ /* ranges must be inserted after we are sure it has enough space */
+ ret = insert_data_ranges(map, tmp, insert_list);
+ map->reserved += reserve;
+ return ret;
+}
+
+/*
* Init data_rsv_map for a given inode.
*
* This is needed at write time as quota can be disabled and then enabled
--
2.5.0
next prev parent reply other threads:[~2015-09-02 7:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 8:54 [PATCH RFC 00/14] Qgroup reserved space fixing framework Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 01/14] btrfs: qgroup: New function declaration for new reserve implement Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 02/14] btrfs: qgroup: Implement data_rsv_map init/free functions Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 03/14] btrfs: qgroup: Introduce new function to search most left reserve range Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 04/14] btrfs: qgroup: Introduce function to insert non-overlap " Qu Wenruo
2015-08-31 8:54 ` Qu Wenruo [this message]
2015-08-31 8:54 ` [PATCH RFC 06/14] btrfs: qgroup: Introduce btrfs_qgroup_reserve_data function Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 07/14] btrfs: qgroup: Introduce function to release reserved range Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 08/14] btrfs: qgroup: Introduce function to release/free reserved data range Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 09/14] btrfs: delayed_ref: Add new function to record reserved space into delayed ref Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 10/14] btrfs: delayed_ref: release and free qgroup reserved at proper timing Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 11/14] btrfs: qgroup: Introduce new functions to reserve/free metadata Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 12/14] btrfs: qgroup: Use new metadata reservation Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 13/14] btrfs: extent-tree: Add new verions of btrfs_check_data_free_space Qu Wenruo
2015-08-31 8:54 ` [PATCH RFC 14/14] btrfs: Use new check_data_free_space for buffered write Qu Wenruo
2015-08-31 8:54 ` [PATCH 15/15] btrfs: fallocate: Add support to accurate qgroup reserve Qu Wenruo
-- strict thread matches above, loose matches on Subject: below --
2015-09-01 0:31 [PATCH RFC 00/14] Qgroup reserved space fixing framework Qu Wenruo
2015-09-01 0:31 ` [PATCH RFC 05/14] btrfs: qgroup: Introduce function to reserve data range per inode Qu Wenruo
2015-09-01 7:21 [PATCH RFC 00/14] Qgroup reserved space fixing framework Qu Wenruo
2015-09-01 8:45 ` [PATCH RFC 05/14] btrfs: qgroup: Introduce function to reserve data range per inode 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=1441011286-23733-6-git-send-email-quwenruo@cn.fujitsu.com \
--to=quwenruo@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 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).