Re: [PATCH] Btrfs: avoid unnecessarily locking inode when clearing a range

2017-08-03 Thread Chris Mason
On 08/03/2017 11:25 AM, Wang Shilong wrote: On Thu, Aug 3, 2017 at 11:00 PM, Chris Mason wrote: On 07/27/2017 02:52 PM, fdman...@kernel.org wrote: From: Filipe Manana If the range being cleared was not marked for defrag and we are not about to clear the

Re: [PATCH] Btrfs: avoid unnecessarily locking inode when clearing a range

2017-08-03 Thread Wang Shilong
On Thu, Aug 3, 2017 at 11:00 PM, Chris Mason wrote: > > > On 07/27/2017 02:52 PM, fdman...@kernel.org wrote: >> >> From: Filipe Manana >> >> If the range being cleared was not marked for defrag and we are not >> about to clear the range from the defrag status, we

Re: [PATCH] Btrfs: avoid unnecessarily locking inode when clearing a range

2017-08-03 Thread Chris Mason
On 07/27/2017 02:52 PM, fdman...@kernel.org wrote: From: Filipe Manana If the range being cleared was not marked for defrag and we are not about to clear the range from the defrag status, we don't need to lock and unlock the inode. Signed-off-by: Filipe Manana

[PATCH] Btrfs: avoid unnecessarily locking inode when clearing a range

2017-07-27 Thread fdmanana
From: Filipe Manana If the range being cleared was not marked for defrag and we are not about to clear the range from the defrag status, we don't need to lock and unlock the inode. Signed-off-by: Filipe Manana --- fs/btrfs/inode.c | 7 --- 1 file