From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, hmsjwzb <weizhefix@gmail.com>
Cc: clm@fb.com, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>, Omar Sandoval <osandov@fb.com>,
Filipe Manana <fdmanana@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Change the total_dirty from SZ_256M to SZ_64M.
Date: Sat, 3 Nov 2018 17:17:58 +0800 [thread overview]
Message-ID: <52fc83c0-4455-0d1b-0fee-42cfdec2580b@gmx.com> (raw)
In-Reply-To: <8965ea1d-c29f-7bdf-44cb-874511899567@suse.com>
On 2018/11/3 下午5:01, Nikolay Borisov wrote:
>
>
> On 3.11.18 г. 10:36 ч., hmsjwzb wrote:
>> The SZ_256M will cause trouble in platform with less than 256M memory.
>> For example, a qemu virtual machine.
>>
>> Signed-off-by: hmsjwzb <weizhefix@gmail.com>
>
> If you have actually taken the care to understand the code in
> test_find_delalloc you would have seen that total_dirty and max_bytes
> are actually inter-dependent so you cannot really change total_bytes
> without adjusting max_bytes as well. Otherwise tests will start breaking.
Nowadays even for VM, the memory size should start from 2G.
If this 256M is causing problem, one should really re-consider the
memory size of the VM.
Not to mention the magic number is two ensure we have at least 2 file
extents.
>
> NACK on this (and likely any future postings of this) since the tests
> are sized in a such a way so as to test design limits (such as the max
> extent size which is 128MB)
And we should add some comment about this.
Personally I prefer some comment with this and also use (2 *
BTRFS_MAX_EXTENT_SIZE) other than this intermediate number.
Thanks,
Qu
>
>
>> ---
>> fs/btrfs/tests/extent-io-tests.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/btrfs/tests/extent-io-tests.c b/fs/btrfs/tests/extent-io-tests.c
>> index 9e0f4a01be14..cb23dce96a2d 100644
>> --- a/fs/btrfs/tests/extent-io-tests.c
>> +++ b/fs/btrfs/tests/extent-io-tests.c
>> @@ -62,7 +62,7 @@ static int test_find_delalloc(u32 sectorsize)
>> struct page *page;
>> struct page *locked_page = NULL;
>> unsigned long index = 0;
>> - u64 total_dirty = SZ_256M;
>> + u64 total_dirty = SZ_64M;
>> u64 max_bytes = SZ_128M;
>> u64 start, end, test_start;
>> u64 found;
>>
prev parent reply other threads:[~2018-11-03 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-03 8:36 hmsjwzb
2018-11-03 9:01 ` Nikolay Borisov
2018-11-03 9:17 ` Qu Wenruo [this message]
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=52fc83c0-4455-0d1b-0fee-42cfdec2580b@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nborisov@suse.com \
--cc=osandov@fb.com \
--cc=weizhefix@gmail.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
all inboxes | Powered by JetHome®