All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] btrfs-progs: Metadata preallocation enhancement
Date: Wed, 5 Jun 2019 18:39:19 +0200	[thread overview]
Message-ID: <20190605163919.GG9896@twin.jikos.cz> (raw)
In-Reply-To: <20190416102144.12173-1-wqu@suse.com>

On Tue, Apr 16, 2019 at 06:21:42PM +0800, Qu Wenruo wrote:
> This patchset will address the github issue #123 to make btrfs-convert
> less possible to report false ENOSPC.
> 
> The first patch will try to avoid the nested chunk/extent tree
> modification in a more explicit way.
> 
> The 2nd patch will address the ENOSPC problem, by adding CSUM tree to
> the metadata preallocate list.
> 
> The 2nd patch is not as aggressive as 7a12d8470e5f ("btrfs-progs:
> Do metadata preallocation as long as we're not modifying extent tree").
> Even we have the 1st patch I still prefer to make less modification to
> avoid possible bugs.
> 
> Qu Wenruo (2):
>   btrfs-progs: Avoid nested chunk allocation call
>   btrfs-progs: Do metadata preallocation for fs trees and csum tree

Added to devel, thanks.

      parent reply	other threads:[~2019-06-05 16:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16 10:21 [PATCH 0/2] btrfs-progs: Metadata preallocation enhancement Qu Wenruo
2019-04-16 10:21 ` [PATCH 1/2] btrfs-progs: Avoid nested chunk allocation call Qu Wenruo
2019-04-16 11:22   ` Filipe Manana
2019-04-16 11:32     ` Qu Wenruo
2019-04-16 11:40       ` Filipe Manana
2019-06-05 16:32   ` David Sterba
2019-06-06  0:29     ` Qu Wenruo
2019-04-16 10:21 ` [PATCH 2/2] btrfs-progs: Do metadata preallocation for fs trees and csum tree Qu Wenruo
2019-06-05 16:39 ` David Sterba [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=20190605163919.GG9896@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.