[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20181103083654.655-1-weizhefix@gmail.com>
Date: Sat, 3 Nov 2018 16:36:53 +0800
From: hmsjwzb <weizhefix@...il.com>
To: unlisted-recipients:; (no To-header on input)
Cc: clm@...com, hmsjwzb <weizhefix@...il.com>,
Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>,
Omar Sandoval <osandov@...com>,
Filipe Manana <fdmanana@...e.com>, linux-btrfs@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [PATCH] Change the total_dirty from SZ_256M to SZ_64M.
The SZ_256M will cause trouble in platform with less than 256M memory.
For example, a qemu virtual machine.
Signed-off-by: hmsjwzb <weizhefix@...il.com>
---
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;
--
2.17.1
Powered by blists - more mailing lists