Searched hist:d278850eff3053ef166cf64c16f798dfe36278a2 (Results 1 – 6 of 6) sorted by relevance
| /openbmc/linux/fs/btrfs/ |
| H A D | delayed-ref.h | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
| H A D | delayed-ref.c | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
| H A D | backref.c | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
| H A D | extent-tree.c | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
| H A D | disk-io.c | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|
| /openbmc/linux/include/trace/events/ |
| H A D | btrfs.h | diff d278850eff3053ef166cf64c16f798dfe36278a2 Fri Sep 29 14:43:57 CDT 2017 Josef Bacik <josef@toxicpanda.com> btrfs: remove delayed_ref_node from ref_head
This is just excessive information in the ref_head, and makes the code
complicated. It is a relic from when we had the heads and the refs in
the same tree, which is no longer the case. With this removal I've
cleaned up a bunch of the cruft around this old assumption as well.
Signed-off-by: Josef Bacik <jbacik@fb.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
|