Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Wang Yugui <wangyugui@e16-tech.com>, Qu Wenruo <wqu@suse.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: simple Chunk allocator like calculation to replace Factor based calculation
Date: Fri, 2 Oct 2020 09:46:25 +0800	[thread overview]
Message-ID: <6941eed6-19a3-add6-6608-8a5d5ec86006@gmx.com> (raw)
In-Reply-To: <20201002093001.19E0.409509F4@e16-tech.com>


[-- Attachment #1.1: Type: text/plain, Size: 2128 bytes --]



On 2020/10/2 上午9:30, Wang Yugui wrote:
> Hi, Qu Wenruo
> 
>> On 2020/10/1 下午11:36, Wang Yugui wrote:
>>> Hi, Qu Wenruo
>>>
>>> Chunk allocator like calculation will get the right value, but it is
>>> slow for big file system such as 500T.
>>
>> Nope, the ballon allocator doesn't have any size limit, thus it will try
>> to use as much space as possible in a single run.
>>
>> If the 500T fs only has say 100T used, and the remaining 400T is split
>> into, say 2 parts, then just two small run would finish.
>>
>> On the other hand, if the 500T is mostly used, only 100T unallocated and
>> the 100T is in a big unallocate chunk (under most cases it's true), then
>> just one allocation run is enough.
>>
>> So in short, it's unrelated to the fs, but how fragmented the
>> unallocated space is.
>> And normally unallocated space is not fragmented at all, thus it's very
>> speedy.
> 
> We need some more complex example for 'Chunk allocator like calculation'
> to make it easy to understand.
> 
> such as
> 1) RAID10 with 8T,1T,1T,1T,1T
>     the virtal chunk size of 1st iteration:	1T or 0.33T?
>     1T    chunk will use 4T at most
>     0.33T chunk will use 5.33T at most?

You didn't get the point.
For the each loop we:
- Sort the devices with their free space.
  In this case, it's 8, 1, 1, 1, 1.

- Round down to dev increament
  Then we got 8, 1, 1, 1.

- Then allocate chunk
  Since the biggest unallocated space is 1T, we allocate a RAID10 with
  1T stripe size, which will be a 2T chunk.

  The remaining size is 7, 0, 0, 0, 1.

- We go to next round.
  No way to allocate new chunk.

In this case, we can only get 2T chunk.
Just as the chunk allocator do.

> 
> 2) RAID10 with 8T,1T,1T,1T,0.5T
>     the virtal chunk size of 1st iteration:0.5T or smaller?

Still the same, 2T chunk can be allocated using the largest 4 devices.

Thanks,
Qu

> 
> Best Regards
> 王玉贵
> 2020/10/02
> 
> 
> --------------------------------------
> 北京京垓科技有限公司
> 王玉贵	wangyugui@e16-tech.com
> 电话:+86-136-71123776
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-10-02  1:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201001212617.82BC.409509F4@e16-tech.com>
     [not found] ` <20201001233649.888B.409509F4@e16-tech.com>
2020-10-01 23:38   ` simple Chunk allocator like calculation to replace Factor based calculation Qu Wenruo
2020-10-02  1:30     ` Wang Yugui
2020-10-02  1:46       ` Qu Wenruo [this message]
2020-10-02  1:59         ` Wang Yugui
2020-10-02  3:06           ` Qu Wenruo
2020-10-02  9:01             ` Wang Yugui
2020-10-02  9:15               ` Qu Wenruo
2020-10-02  9:06             ` Wang Yugui
2020-10-02 10:13               ` Hugo Mills
2020-10-02 10:23                 ` Hugo Mills

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=6941eed6-19a3-add6-6608-8a5d5ec86006@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangyugui@e16-tech.com \
    --cc=wqu@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