linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wang Xiaoguang <wangxg.fnst@cn.fujitsu.com>
To: dsterba@suse.cz,
	"Holger Hoffstätte" <holger@applied-asynchrony.com>,
	linux-btrfs@vger.kernel.org, jbacik@fb.com, dsterba@suse.com
Subject: Re: [PATCH 2/2] btrfs: fix false enospc for compression
Date: Tue, 25 Oct 2016 18:43:18 +0800	[thread overview]
Message-ID: <580F3746.3030509@cn.fujitsu.com> (raw)
In-Reply-To: <20161019142344.GR11398@twin.jikos.cz>

hi,

On 10/19/2016 10:23 PM, David Sterba wrote:
> On Mon, Oct 17, 2016 at 05:01:46PM +0800, Wang Xiaoguang wrote:
>>> [..]
>>>>    int btrfs_set_extent_delalloc(struct inode *inode, u64 start, u64 end,
>>>> -			      struct extent_state **cached_state);
>>>> +			      struct extent_state **cached_state, int flag);
>>>>    int btrfs_set_extent_defrag(struct inode *inode, u64 start, u64 end,
>>>> -			    struct extent_state **cached_state);
>>>> +			    struct extent_state **cached_state, int flag);
>>> [..]
>>>>    int btrfs_dirty_pages(struct btrfs_root *root, struct inode *inode,
>>>>    		      struct page **pages, size_t num_pages,
>>>>    		      loff_t pos, size_t write_bytes,
>>>> -		      struct extent_state **cached);
>>>> +		      struct extent_state **cached, int flag);
>>> Instead of adding "int flag" why not use the already defined
>>> btrfs_metadata_reserve_type enum? I know it's just an int at the end of
>>> the day, but the dedupe support already added another "int dedupe" argument
>>> and it's probably easy to cause confusion.
>>> Maybe later it would be beneficial to consolidate the flags into a consistent
>>> set of enum values to prevent more "int flag" inflation and better declare the
>>> intent of the extent state change. Not sure if that makes sense.
>> Yes, agree.
>> I'll rebase them later, thanks.
> Would be great. I won't manually merge the patch now as it's not a
> conflict against the current state, btrfs_set_extent_delalloc has the
> extra parameter already. Please consolidate them before this patch is
> supposed to be merged. Thanks.
Sorry for being late, I have just finished the rebase work now.
I'll run some fstests job, if no regressions, I'll send two patches 
tomorrow :)

Regards,
Xiaoguang Wang

>
>




  reply	other threads:[~2016-10-25 10:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-06  2:51 [PATCH 1/2] btrfs: improve inode's outstanding_extents computation Wang Xiaoguang
2016-10-06  2:51 ` [PATCH 2/2] btrfs: fix false enospc for compression Wang Xiaoguang
2016-10-06  3:51   ` Wang Xiaoguang
2016-10-12  3:12   ` Wang Xiaoguang
2016-10-17 15:05     ` David Sterba
2016-10-14 13:09   ` Stefan Priebe - Profihost AG
2016-10-14 13:59   ` Holger Hoffstätte
2016-10-17  9:01     ` Wang Xiaoguang
2016-10-19 14:23       ` David Sterba
2016-10-25 10:43         ` Wang Xiaoguang [this message]
2016-10-14 13:09 ` [PATCH 1/2] btrfs: improve inode's outstanding_extents computation Stefan Priebe - Profihost AG
2016-10-23 17:45   ` Stefan Priebe - Profihost AG
  -- strict thread matches above, loose matches on Subject: below --
2016-11-01 10:18 Wang Xiaoguang
2016-11-01 10:18 ` [PATCH 2/2] btrfs: fix false enospc for compression Wang Xiaoguang
2016-11-01 10:28   ` 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=580F3746.3030509@cn.fujitsu.com \
    --to=wangxg.fnst@cn.fujitsu.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=holger@applied-asynchrony.com \
    --cc=jbacik@fb.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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).