Searched hist:"70 c8a91ce21b83ccd2d9e7c968775430ead4353d" (Results 1 – 7 of 7) sorted by relevance
| /openbmc/linux/fs/btrfs/ |
| H A D | extent_map.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | ctree.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | tree-log.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | file.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | volumes.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | ctree.h | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
| H A D | inode.c | diff 70c8a91ce21b83ccd2d9e7c968775430ead4353d Thu Oct 11 15:54:30 CDT 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: log changed inodes based on the extent map tree
We don't really need to copy extents from the source tree since we have all
of the information already available to us in the extent_map tree. So
instead just write the extents straight to the log tree and don't bother to
copy the extent items from the source tree.
Signed-off-by: Josef Bacik <jbacik@fusionio.com>
Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|