bcachefs: Re-implement extent merging in transaction commit path
We haven't had extent merging in quite some time. It used to be done by the btree code when sorting btree nodes, but that was eliminated as part of the work to separate extent handling from core btree code. This patch re-implements extent merging in the transaction commit path. We don't currently have the ability to merge reflink pointers, we need to do some work on the triggers code to be able to do that without ending up with incorrect refcounts. Signed-off-by: Kent Overstreet <kent.overstreet@gmail.com>
This commit is contained in:
committed by
Kent Overstreet
parent
81d22e5d83
commit
5db95e50e1
@ -51,10 +51,7 @@ static inline bool bch2_bkey_maybe_mergable(const struct bkey *l, const struct b
|
||||
{
|
||||
return l->type == r->type &&
|
||||
!bversion_cmp(l->version, r->version) &&
|
||||
!bpos_cmp(l->p, bkey_start_pos(r)) &&
|
||||
(u64) l->size + r->size <= KEY_SIZE_MAX &&
|
||||
bch2_bkey_ops[l->type].key_merge &&
|
||||
!bch2_key_merging_disabled;
|
||||
!bpos_cmp(l->p, bkey_start_pos(r));
|
||||
}
|
||||
|
||||
bool bch2_bkey_merge(struct bch_fs *, struct bkey_s, struct bkey_s_c);
|
||||
|
Reference in New Issue
Block a user