Re: [PATCH] Btrfs: don't be as agressive with delalloc metadata reservations V2

2011-07-21 Thread Christian Brunner
2011/7/18 Josef Bacik : > On 07/18/2011 02:11 PM, Josef Bacik wrote: >> Currently we reserve enough space to COW an entirely full btree for every >> extent >> we have reserved for an inode.  This _sucks_, because you only need to COW >> once, >> and then everybody else is ok.  Unfortunately we do

Re: [PATCH] Btrfs: don't be as agressive with delalloc metadata reservations V2

2011-07-18 Thread Josef Bacik
On 07/18/2011 02:11 PM, Josef Bacik wrote: > Currently we reserve enough space to COW an entirely full btree for every > extent > we have reserved for an inode. This _sucks_, because you only need to COW > once, > and then everybody else is ok. Unfortunately we don't know we'll all be able > t

[PATCH] Btrfs: don't be as agressive with delalloc metadata reservations V2

2011-07-18 Thread Josef Bacik
Currently we reserve enough space to COW an entirely full btree for every extent we have reserved for an inode. This _sucks_, because you only need to COW once, and then everybody else is ok. Unfortunately we don't know we'll all be able to get into the same transaction so that's what we have had

Re: [PATCH] Btrfs: don't be as agressive with delalloc metadata reservations

2011-07-18 Thread Josef Bacik
On 07/17/2011 11:04 PM, liubo wrote: > On 07/16/2011 02:29 AM, Josef Bacik wrote: >> Currently we reserve enough space to COW an entirely full btree for every >> extent >> we have reserved for an inode. This _sucks_, because you only need to COW >> once, >> and then everybody else is ok. Unfort

Re: [PATCH] Btrfs: don't be as agressive with delalloc metadata reservations

2011-07-17 Thread liubo
On 07/16/2011 02:29 AM, Josef Bacik wrote: > Currently we reserve enough space to COW an entirely full btree for every > extent > we have reserved for an inode. This _sucks_, because you only need to COW > once, > and then everybody else is ok. Unfortunately we don't know we'll all be able > t

[PATCH] Btrfs: don't be as agressive with delalloc metadata reservations

2011-07-15 Thread Josef Bacik
Currently we reserve enough space to COW an entirely full btree for every extent we have reserved for an inode. This _sucks_, because you only need to COW once, and then everybody else is ok. Unfortunately we don't know we'll all be able to get into the same transaction so that's what we have had