Searched hist:b11e234d21e73df94099e473a080bca502b9a496 (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/fs/btrfs/ |
H A D | extent_map.h | diff b11e234d21e73df94099e473a080bca502b9a496 Mon Dec 03 09:58:15 CST 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: do not mark ems as prealloc if we are writing to them
We are going to use EM's to log extents in the future, so we need to not mark them as prealloc if they aren't actually prealloc extents. Instead mark them with FILLING so we know to ammend mod_start/mod_len and that way we don't confuse the extent logging code. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
H A D | extent_map.c | diff b11e234d21e73df94099e473a080bca502b9a496 Mon Dec 03 09:58:15 CST 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: do not mark ems as prealloc if we are writing to them
We are going to use EM's to log extents in the future, so we need to not mark them as prealloc if they aren't actually prealloc extents. Instead mark them with FILLING so we know to ammend mod_start/mod_len and that way we don't confuse the extent logging code. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|
H A D | inode.c | diff b11e234d21e73df94099e473a080bca502b9a496 Mon Dec 03 09:58:15 CST 2012 Josef Bacik <jbacik@fusionio.com> Btrfs: do not mark ems as prealloc if we are writing to them
We are going to use EM's to log extents in the future, so we need to not mark them as prealloc if they aren't actually prealloc extents. Instead mark them with FILLING so we know to ammend mod_start/mod_len and that way we don't confuse the extent logging code. Thanks,
Signed-off-by: Josef Bacik <jbacik@fusionio.com> Signed-off-by: Chris Mason <chris.mason@fusionio.com>
|