Searched hist:"89573 b9c516b24af8a3b9958dd5afca8fa874e3d" (Results 1 – 1 of 1) sorted by relevance
| /openbmc/linux/fs/btrfs/ |
| H A D | transaction.c | diff 89573b9c516b24af8a3b9958dd5afca8fa874e3d Thu Mar 12 19:12:45 CDT 2009 Chris Mason <chris.mason@oracle.com> 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>
|