Linux bcachefs list
 help / color / mirror / Atom feed
* Unused trace events in bcachefs
@ 2025-06-13  2:40 Steven Rostedt
  0 siblings, 0 replies; only message in thread
From: Steven Rostedt @ 2025-06-13  2:40 UTC (permalink / raw)
  To: LKML; +Cc: Kent Overstreet, linux-bcachefs

I have code that will trigger a warning if a trace event is defined but
not used[1]. It gives a list of unused events. Here's what I have for
bcachefs:

warning: tracepoint 'trans_restart_journal_preres_get' is unused.
warning: tracepoint 'trans_restart_fault_inject' is unused.
warning: tracepoint 'trans_restart_relock_after_fill' is unused.
warning: tracepoint 'trans_restart_key_cache_upgrade' is unused.
warning: tracepoint 'trans_restart_relock_key_cache_fill' is unused.
warning: tracepoint 'trans_restart_traverse' is unused.
warning: tracepoint 'trans_restart_key_cache_key_realloced' is unused.
warning: tracepoint 'trans_restart_write_buffer_flush' is unused.
warning: tracepoint 'btree_path_free_trans_begin' is unused.

Each trace event can take up to around 5K in memory regardless if they
are used or not. Soon there will be warnings when they are defined but
not used. Please remove any unused trace event or at least hide it
under an #ifdef if they are used within configs. I'm planning on adding
these warning in the next merge window.

Thanks,

-- Steve

[1] https://lore.kernel.org/linux-trace-kernel/20250612235827.011358765@goodmis.org/

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2025-06-13  2:41 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-06-13  2:40 Unused trace events in bcachefs Steven Rostedt

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox