kernel.git/fs/bcachefs/trace.h, branch linux-6.15.yHosts the 0x221E linux distro kernel.
https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-6.15.y2025-03-24T13:50:34Zbcachefs: trace_io_move_write_fail2025-03-24T13:50:34ZKent Overstreet2025-03-15T23:24:44Zurn:sha1:fb8a9a32ccd2979b4ec77fde01cc585ff2835e55
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: trace_stripe_create2025-03-15T01:02:16ZKent Overstreet2025-03-07T19:30:29Zurn:sha1:434a3f2ffaa1519a562909a92c62b77cf29f05da
Add a simple tracepoint for stripe creation, we'll want to expand this
later.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Read/move path counter work2025-03-15T01:02:12ZKent Overstreet2025-02-04T01:15:52Zurn:sha1:157ea5834133c02cb93e06e6a014cfc0b3b109e5
Reorganize counters a bit, grouping related counters together.
New counters:
- io_read_inline
- io_read_hole
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: bch2_move_data_phys()2025-03-15T01:02:12ZKent Overstreet2024-12-28T15:40:11Zurn:sha1:987fdbdb40293557e59bc27c4bc89ecd715b8019
Add a more general version of bch2_evacuate_bucket - to be used for
scrub.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix discard path journal flushing2025-02-07T03:35:11ZKent Overstreet2025-01-27T06:21:44Zurn:sha1:9e9033522ad1e4bb697c9493aa449630fa2c98d2
The discard path is supposed to issue journal flushes when there's too
many buckets empty buckets that need a journal commit before they can be
written to again, but at some point this code seems to have been lost.
Bring it back with a new optimization to make sure we don't issue too
many journal flushes: the journal now tracks the sequence number of the
most recent flush in progress, which the discard path uses when deciding
which buckets need a journal flush.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix trace_copygc2025-01-27T04:02:28ZKent Overstreet2025-01-17T17:51:51Zurn:sha1:0e458a616f680837d0ba9c3c8ba9f66993db4225
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: trace_key_cache_fill2024-12-29T18:30:39ZKent Overstreet2024-12-13T10:43:00Zurn:sha1:07c1a6fa901dc478a2685614399dedece910d6f5
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: trace_write_buffer_maybe_flush2024-12-21T06:36:23ZKent Overstreet2024-12-10T15:29:12Zurn:sha1:3f57171d8ddd792a0367e05395a6266e5fc011e0
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: trace_accounting_mem_insert2024-12-21T06:36:21ZKent Overstreet2024-12-04T22:44:25Zurn:sha1:400af9a398186851103e27d848ef42be8870072b
Add a tracepoint for inserting new accounting entries: we're seeing odd
spinning behaviour in accounting read.
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>
bcachefs: Fix evacuate_bucket tracepoint2024-12-21T06:36:18ZKent Overstreet2024-12-09T11:18:49Zurn:sha1:4de2c24aa9453564ceb285039e2816bd22fa4ac6
86a494c8eef9 ("bcachefs: Kill bch2_get_next_backpointer()") dropped some
things the tracepoint emitted because bch2_evacuate_bucket() no longer
looks at the alloc key - but we did want at least some of that.
We still no longer look at the alloc key so we can't report on the
fragmentation number, but that's a direct function of dirty_sectors and
a copygc concern anyways - copygc should get its own tracepoint that
includes information from the fragmentation LRU.
But we can report on the number of sectors we moved and the bucket size.
Co-developed-by: Piotr Zalewski <pZ010001011111@proton.me>
Signed-off-by: Kent Overstreet <kent.overstreet@linux.dev>