Btrfs: Only let very young transactions grow during commit
authorChris Mason <chris.mason@oracle.com>
Fri, 13 Mar 2009 00:12:45 +0000 (20:12 -0400)
committerChris Mason <chris.mason@oracle.com>
Tue, 24 Mar 2009 20:14:28 +0000 (16:14 -0400)
commit89573b9c516b24af8a3b9958dd5afca8fa874e3d
tree77b622ea49234d3383882ed0050e8910b4d99adb
parent66d7e85ea7c3628189d19b265495358f756cb463
Btrfs: Only let very young transactions grow during commit

Commits are fairly expensive, and so btrfs has code to sit around for a while
during the commit and let new writers come in.

But, while we're sitting there, new delayed refs might be added, and those
can be expensive to process as well.  Unless the transaction is very very
young, it makes sense to go ahead and let the commit finish without hanging
around.

The commit grow loop isn't as important as it used to be, the fsync logging
code handles most performance critical syncs now.

Signed-off-by: Chris Mason <chris.mason@oracle.com>
fs/btrfs/transaction.c