hello,
On 07/20/2016 09:22 PM, Josef Bacik wrote:
On 07/20/2016 01:56 AM, Wang Xiaoguang wrote:
In next patch, btrfs_clear_bit_hook() will not call
btrfs_free_reserved_data_space_noquota() to update btrfs_space_info's
bytes_may_use unless it has EXTENT_DO_ACCOUNTING or
EXTENT_CLEAR_DATA_RESV,
as for the reason, please see the next patch for detailed info.
As we know, usually EXTENT_DO_ACCOUNTING is used for error path. In
run_delalloc_nocow(), for inode marked as NODATACOW or extent marked as
PREALLOC, we also need to update bytes_may_use, but can not pass
EXTENT_DO_ACCOUNTING, because it also clears metadata reservation, so
here
we introduce EXTENT_CLEAR_DATA_RESV flag to indicate
btrfs_clear_bit_hook()
to update btrfs_space_info's bytes_may_use.
Signed-off-by: Wang Xiaoguang <wangxg.f...@cn.fujitsu.com>
There's no point in introducing only a flag in one patch, collapse
this into the patch that actually uses it. Thanks,
OK
Regards,
Xiaoguang Wang
Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
