linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com
Subject: Re: [PATCH] btrfs: limit the number of asynchronous delalloc pages to reasonable value
Date: Tue, 22 Nov 2016 13:40:50 +0100	[thread overview]
Message-ID: <20161122124050.GL12522@suse.cz> (raw)
In-Reply-To: <58340DCA.7050107@cn.fujitsu.com>

On Tue, Nov 22, 2016 at 05:20:10PM +0800, Wang Xiaoguang wrote:
> hello,
> 
> On 11/22/2016 12:39 AM, David Sterba wrote:
> > On Tue, Nov 08, 2016 at 05:30:58PM +0800, Wang Xiaoguang wrote:
> >> The current limit of number of asynchronous delalloc pages is (10 * SZ_1M).
> >> For 4K page, the total ram bytes would be 40G, very big value, I think in
> >> most cases, this limit will not work, here I set limit of the number of
> >> asynchronous delalloc pages to SZ_1M(4GB ram bytes).
> >>
> >> Signed-off-by: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
> >> ---
> >>   fs/btrfs/inode.c | 2 +-
> >>   1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/fs/btrfs/inode.c b/fs/btrfs/inode.c
> >> index 8e3a5a2..3a910f6 100644
> >> --- a/fs/btrfs/inode.c
> >> +++ b/fs/btrfs/inode.c
> >> @@ -1158,7 +1158,7 @@ static int cow_file_range_async(struct inode *inode, struct page *locked_page,
> >>   	struct btrfs_root *root = BTRFS_I(inode)->root;
> >>   	unsigned long nr_pages;
> >>   	u64 cur_end;
> >> -	int limit = 10 * SZ_1M;
> >> +	int limit = SZ_1M;
> > This looks like mismatch in units, the limit seems to be "10MiB" but
> > it's used to compare async_delalloc_pages, which is in pages. I'm not
> > sure what's the expected value for limit, as 10MiB is too small.
> There are such codes in cow_file_range_async()
>      nr_pages = (cur_end - start + PAGE_SIZE) >> PAGE_SHIFT;
>      atomic_add(nr_pages, &root->fs_info->async_delalloc_pages);
> 
> So here the real limit is 10 * SZ_1M * 4096, 40GB memory, I think this
> value is too big, so modify it to 4GB.

Yeah, but I don't see why 4GB would be a good value either.

  reply	other threads:[~2016-11-22 12:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-08  9:30 [PATCH] btrfs: limit the number of asynchronous delalloc pages to reasonable value Wang Xiaoguang
2016-11-21 16:39 ` David Sterba
2016-11-22  9:20   ` Wang Xiaoguang
2016-11-22 12:40     ` David Sterba [this message]
2016-11-22 14:32     ` Chris Mason
2016-11-21 17:59 ` Chris Mason
2016-11-22  9:30   ` Wang Xiaoguang

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=20161122124050.GL12522@suse.cz \
    --to=dsterba@suse.cz \
    --cc=clm@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=wangxg.fnst@cn.fujitsu.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).