linux.git/fs/bcachefs/sysfs.c, branch v6.9 Linux kernel source tree bcachefs: sysfs internal/trigger_journal_flush 2024-04-15T00:02:11+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-04-14T02:43:11+00:00 bdae2a7e6020e1cf864a30dab2af323575569dc7 Add a sysfs knob for immediately flushing the entire journal. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Add a sysfs knob for immediately flushing the entire journal.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Move btree_updates to debugfs 2024-04-04T20:56:44+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-04-03T23:15:53+00:00 9fb3036fe3d9414ae32a97d01d7ccf7550e168a7 sysfs is limited to PAGE_SIZE, and when we're debugging strange deadlocks/priority inversions we need to see the full list. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
sysfs is limited to PAGE_SIZE, and when we're debugging strange
deadlocks/priority inversions we need to see the full list.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: time_stats: split stats-with-quantiles into a separate structure 2024-03-14T01:38:01+00:00 Darrick J. Wong djwong@kernel.org 2024-02-01T20:41:42+00:00 273960b8f374b95ebd234a99607b7887f515c791 Currently, struct time_stats has the optional ability to quantize the information that it collects. This is /probably/ useful for callers who want to see quantized information, but it more than doubles the size of the structure from 224 bytes to 464. For users who don't care about that (e.g. upcoming xfs patches) and want to avoid wasting 240 bytes per counter, split the two into separate pieces. Signed-off-by: Darrick J. Wong <djwong@kernel.org> Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Currently, struct time_stats has the optional ability to quantize the
information that it collects.  This is /probably/ useful for callers who
want to see quantized information, but it more than doubles the size of
the structure from 224 bytes to 464.  For users who don't care about
that (e.g. upcoming xfs patches) and want to avoid wasting 240 bytes per
counter, split the two into separate pieces.

Signed-off-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: opts->compression can now also be applied in the background 2024-01-21T18:27:10+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-16T21:20:21+00:00 d7e77f53e90e1eb87838eed7c651531427b9114a The "apply this compression method in the background" paths now use the compression option if background_compression is not set; this means that setting or changing the compression option will cause existing data to be compressed accordingly in the background. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
The "apply this compression method in the background" paths now use the
compression option if background_compression is not set; this means that
setting or changing the compression option will cause existing data to
be compressed accordingly in the background.

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_prt_compression_type() 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-07T02:01:47+00:00 4f564f4f9fdd4d120ee04678b0c22e40cc8b6b47 bounds checking helper, since compression types are extensible Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
bounds checking helper, since compression types are extensible

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: helpers for printing data types 2024-01-21T11:01:45+00:00 Kent Overstreet kent.overstreet@linux.dev 2024-01-07T01:57:43+00:00 e58f963cecbdb08f28334122afba93a7840beabc We need bounds checking since new versions may introduce new data types. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
We need bounds checking since new versions may introduce new data types.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: for_each_btree_key() now declares loop iter 2024-01-01T16:47:42+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-17T03:30:09+00:00 80eab7a7c2808f84e56ba1f2f1408a16c46d3bdc Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Rename for_each_btree_key2() -> for_each_btree_key() 2024-01-01T16:47:40+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-12-08T04:33:11+00:00 5028b9078ccb02ead012056dcbcc4f27f963b212 Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: convert bch_fs_flags to x-macro 2024-01-01T16:47:38+00:00 Kent Overstreet kent.overstreet@linux.dev 2023-11-26T22:05:02+00:00 3c471b65889aa22d6ba4f8e3d2e5006bb70fdb58 Now we can print out filesystem flags in sysfs, useful for debugging various "what's my filesystem doing" issues. Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev> 
Now we can print out filesystem flags in sysfs, useful for debugging
various "what's my filesystem doing" issues.

Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>