Btrfs: don't mix the ordered extents of all files together during logging the inodes

Browse source

There was a problem in the old code:
If we failed to log the csum, we would free all the ordered extents in the log list
including those ordered extents that were logged successfully, it would make the
log committer not to wait for the completion of the ordered extents.

This patch doesn't insert the ordered extents that is about to be logged into
a global list, instead, we insert them into a local list. If we log the ordered
extents successfully, we splice them with the global list, or we will throw them
away, then do full sync. It can also reduce the lock contention and the traverse
time of list.

Signed-off-by: Miao Xie <miaox@cn.fujitsu.com>
Signed-off-by: Josef Bacik <jbacik@fb.com>

...

This commit is contained in:

Miao Xie 2014-01-14 20:31:51 +08:00 • committed by Josef Bacik

parent 93de4ba864

commit 827463c49f

3 changed files with 49 additions and 35 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

37

fs/btrfs/ordered-data.c

View file

6

fs/btrfs/ordered-data.h

View file

41

fs/btrfs/tree-log.c

View file