From: Su Yue <suy.fnst@cn.fujitsu.com>
To: Nikolay Borisov <nborisov@suse.com>, <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC PATCH 01/17] btrfs: priority alloc: prepare of priority aware allocator
Date: Wed, 28 Nov 2018 17:24:18 +0800 [thread overview]
Message-ID: <989b9bb8-991a-438e-90d4-b0998541949e@cn.fujitsu.com> (raw)
In-Reply-To: <3abe66e9-d836-71d1-8e93-8facc8a5576a@suse.com>
On 11/28/18 4:24 PM, Nikolay Borisov wrote:
>
>
> On 28.11.18 г. 5:11 ч., Su Yue wrote:
>> To implement priority aware allocator, this patch:
>> Introduces struct btrfs_priority_tree which contains block groups
>> in same level.
>> Adds member priority to struct btrfs_block_group_cache and pointer
>> points to the priority tree it's located.
>>
>> Adds member priority_trees to struct btrfs_space_info to represents
>> priority trees in different raid types.
>>
>> Signed-off-by: Su Yue <suy.fnst@cn.fujitsu.com>
>> ---
>> fs/btrfs/ctree.h | 24 ++++++++++++++++++++++++
>> 1 file changed, 24 insertions(+)
>>
>> diff --git a/fs/btrfs/ctree.h b/fs/btrfs/ctree.h
>> index e62824cae00a..5c4651d8a524 100644
>> --- a/fs/btrfs/ctree.h
>> +++ b/fs/btrfs/ctree.h
>> @@ -437,6 +437,8 @@ struct btrfs_space_info {
>> struct rw_semaphore groups_sem;
>> /* for block groups in our same type */
>> struct list_head block_groups[BTRFS_NR_RAID_TYPES];
>> + /* for priority trees in our same type */
>> + struct rb_root priority_trees[BTRFS_NR_RAID_TYPES];
>> wait_queue_head_t wait;
>>
>> struct kobject kobj;
>> @@ -558,6 +560,21 @@ struct btrfs_full_stripe_locks_tree {
>> struct mutex lock;
>> };
>>
>> +/*
>> + * Tree to record all block_groups in same priority level.
>> + * Only used in priority aware allocator.
>> + */
>> +struct btrfs_priority_tree {
>> + /* protected by groups_sem */
>> + struct rb_root block_groups;
>> + struct rw_semaphore groups_sem;
>> +
>> + /* for different level priority trees in same index*/
>> + struct rb_node node;
>> +
>> + int level;
>
> Do you ever expect the level to be a negative number? If not then use
> u8/u32 depending on the range of levels you expect.
>
Indeed, level is not expected to be negative. u8 is more proper.
>> +};
>> +
>> struct btrfs_block_group_cache {
>> struct btrfs_key key;
>> struct btrfs_block_group_item item;
>> @@ -571,6 +588,8 @@ struct btrfs_block_group_cache {
>> u64 flags;
>> u64 cache_generation;
>>
>> + /* It's used only when priority aware allocator is enabled. */
>> + long priority;
>
> What's the range of priorities you are expecting, wouldn't an u8 be
> sufficient, that gives us 256 priorities?
>
The 6th patch introduces three special priorities. That's what I called
dirty codes.
Thanks,
Su
>> /*
>> * If the free space extent count exceeds this number, convert the block
>> * group to bitmaps.
>> @@ -616,6 +635,9 @@ struct btrfs_block_group_cache {
>> /* for block groups in the same raid type */
>> struct list_head list;
>>
>> + /* for block groups in the same priority level */
>> + struct rb_node node;
>> +
>> /* usage count */
>> atomic_t count;
>>
>> @@ -670,6 +692,8 @@ struct btrfs_block_group_cache {
>>
>> /* Record locked full stripes for RAID5/6 block group */
>> struct btrfs_full_stripe_locks_tree full_stripe_locks_root;
>> +
>> + struct btrfs_priority_tree *priority_tree;
>> };
>>
>> /* delayed seq elem */
>>
>
>
next prev parent reply other threads:[~2018-11-28 9:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 3:11 [RFC PATCH 00/17] btrfs: implementation of priority aware allocator Su Yue
2018-11-28 3:11 ` [RFC PATCH 01/17] btrfs: priority alloc: prepare " Su Yue
2018-11-28 8:24 ` Nikolay Borisov
2018-11-28 9:24 ` Su Yue [this message]
2018-11-28 3:11 ` [RFC PATCH 02/17] btrfs: add mount definition BTRFS_MOUNT_PRIORITY_USAGE Su Yue
2018-11-28 3:11 ` [RFC PATCH 03/17] btrfs: priority alloc: introduce compute_block_group_priority/usage Su Yue
2018-11-28 8:56 ` Nikolay Borisov
2018-11-28 3:11 ` [RFC PATCH 04/17] btrfs: priority alloc: add functions to create/remove priority trees Su Yue
2018-11-28 3:11 ` [RFC PATCH 05/17] btrfs: priority alloc: introduce functions to add block group to priority tree Su Yue
2018-11-28 3:11 ` [RFC PATCH 06/17] btrfs: priority alloc: introduce three macros to mark block group status Su Yue
2018-11-28 3:11 ` [RFC PATCH 07/17] btrfs: priority alloc: add functions to remove block group from priority tree Su Yue
2018-11-28 3:11 ` [RFC PATCH 08/17] btrfs: priority alloc: add btrfs_update_block_group_priority() Su Yue
2018-11-28 3:11 ` [RFC PATCH 09/17] btrfs: priority alloc: call create/remove_priority_trees in space_info Su Yue
2018-11-28 3:11 ` [RFC PATCH 10/17] btrfs: priority alloc: call add_block_group_priority while reading or making block group Su Yue
2018-11-28 3:11 ` [RFC PATCH 11/17] btrfs: priority alloc: remove block group from priority tree while removing " Su Yue
2018-11-28 3:11 ` [RFC PATCH 12/17] btrfs: priority alloc: introduce find_free_extent_search() Su Yue
2018-11-28 3:11 ` [RFC PATCH 13/17] btrfs: priority alloc: modify find_free_extent() to fit priority allocator Su Yue
2018-11-28 3:11 ` [RFC PATCH 14/17] btrfs: priority alloc: introduce btrfs_set_bg_updating and call btrfs_update_block_group_prioriy Su Yue
2018-11-28 3:11 ` [RFC PATCH 15/17] btrfs: priority alloc: write bg->priority_groups_sem while waiting reservation Su Yue
2018-11-28 3:11 ` [RFC PATCH 16/17] btrfs: priority alloc: write bg->priority_tree->groups_sem to avoid race in btrfs_delete_unused_bgs() Su Yue
2018-11-28 3:11 ` [RFC PATCH 17/17] btrfs: add mount option "priority_alloc=%s" Su Yue
2018-11-28 4:04 ` [RFC PATCH 00/17] btrfs: implementation of priority aware allocator Qu Wenruo
2018-12-02 5:28 ` Su Yue
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=989b9bb8-991a-438e-90d4-b0998541949e@cn.fujitsu.com \
--to=suy.fnst@cn.fujitsu.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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).