linux.git/fs/bcachefs/btree_trans_commit.c, branch v6.8 Linux kernel source tree bcachefs: add missing __GFP_NOWARN 2024-01-21T18:27:10+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-17T22:16:07+00:00 7be0208fc99207e86974f40a3b57949dae67976c Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Prep work for variable size btree node buffers 2024-01-21T18:27:10+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-16T18:29:59+00:00 ec4edd7b9d2038a97e0ba3fad8fc8492b0d12d35 bcachefs btree nodes are big - typically 256k - and btree roots are pinned in memory. As we're now up to 18 btrees, we now have significant memory overhead in mostly empty btree roots. And in the future we're going to start enforcing that certain btree node boundaries exist, to solve lock contention issues - analagous to XFS's AGIs. Thus, we need to start allocating smaller btree node buffers when we can. This patch changes code that refers to the filesystem constant c->opts.btree_node_size to refer to the btree node buffer size - btree_buf_bytes() - where appropriate. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
bcachefs btree nodes are big - typically 256k - and btree roots are
pinned in memory. As we're now up to 18 btrees, we now have significant
memory overhead in mostly empty btree roots.

And in the future we're going to start enforcing that certain btree node
boundaries exist, to solve lock contention issues - analagous to XFS's
AGIs.

Thus, we need to start allocating smaller btree node buffers when we
can. This patch changes code that refers to the filesystem constant
c->opts.btree_node_size to refer to the btree node buffer size -
btree_buf_bytes() - where appropriate.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: bch2_trans_account_disk_usage_change() 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-11T20:08:36+00:00 5b14ce35af901853e91e186f34e71f31b08b4e0a The disk space accounting rewrite is splitting out accounting for each replicas set - those are moving to btree keys, instead of percpu counters. This breaks bch2_trans_fs_usage_apply() up, splitting out the part we will still need. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
The disk space accounting rewrite is splitting out accounting for each
replicas set - those are moving to btree keys, instead of percpu
counters.

This breaks bch2_trans_fs_usage_apply() up, splitting out the part we
will still need.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: BTREE_TRIGGER_ATOMIC 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-07T22:14:46+00:00 38c23fb809f60bda1adfc431b18200b8f68c2025 Add a new flag to be explicit about when we're running atomic triggers. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Add a new flag to be explicit about when we're running atomic triggers.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Combine .trans_trigger, .atomic_trigger 2024-01-06T04:24:20+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-01T02:01:06+00:00 f0431c5f474643a0dbe9f3c288480422abd16179 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: mark now takes bkey_s 2024-01-06T04:24:19+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:19:09+00:00 ad00bce07da8138c08f6585f153412b65c99b064 Prep work for disk space accounting rewrite: we're going to want to use a single callback for both of our current triggers, so we need to change them to have the same type signature first. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Prep work for disk space accounting rewrite: we're going to want to use
a single callback for both of our current triggers, so we need to change
them to have the same type signature first.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: trans_mark now takes bkey_s 2024-01-06T04:24:19+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-28T04:19:09+00:00 717296c34c8d9d13d7aad4d710b0c3bdb285783b Prep work for disk space accounting rewrite: we're going to want to use a single callback for both of our current triggers, so we need to change them to have the same type signature first. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Prep work for disk space accounting rewrite: we're going to want to use
a single callback for both of our current triggers, so we need to change
them to have the same type signature first.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Check journal entries for invalid keys in trans commit path 2024-01-06T04:24:19+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-21T05:16:32+00:00 5e329145148d7e9fe5a07ecfc08682ef7334a4d1 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix interior update path btree_path uses 2024-01-01T16:47:44+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-15T20:21:40+00:00 ff70ad2c8dfdcc24f98b645481116d4c2ea20e37 Since the btree_paths array is now about to become growable, we have to be careful not to refer to paths by pointer across contexts where they may be reallocated. This fixes the remaining btree_interior_update() paths - split and merge. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Since the btree_paths array is now about to become growable, we have to
be careful not to refer to paths by pointer across contexts where they
may be reallocated.

This fixes the remaining btree_interior_update() paths - split and
merge.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Clean up btree_trans 2024-01-01T16:47:44+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-11T07:31:12+00:00 6474b706108bac9e531a71ddeb8150f8fa17163c Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>