From: Steven Rostedt <rostedt@goodmis.org>
To: 李鹏飞 <ljdlns1987@gmail.com>
Cc: lipengfei28@xiaomi.com, linux-trace-devel@vger.kernel.org
Subject: Re: [RFC IDEA] ftrace: stack trace deduplication in ring buffer
Date: Wed, 13 May 2026 08:51:45 -0400 [thread overview]
Message-ID: <20260513085145.30dd23e0@fedora> (raw)
In-Reply-To: <CALd=Voi=jdM027HTUL01iRnsShcD+rRj5zbRczEN_y4qZ8QQVA@mail.gmail.com>
On Wed, 13 May 2026 11:55:24 +0800
李鹏飞 <ljdlns1987@gmail.com> wrote:
> My question: is this something you'd consider for upstream ftrace,
> or do you feel this belongs in the eBPF/perf domain? If you're open
> to it, I'll prepare a proper RFC patch series addressing:
Yes, this looks appropriate for the tracefs infrastructure.
> - Pre-allocated bucket pool (no GFP_ATOMIC in trace path)
Have you looked at the tracing_map.c code that handles the histograms
for trace events?
> - Per-trace_array instance support
> - rhashtable or similar proven data structure
> - trace-cmd/libtraceevent plugin for stack_id resolution
If it is a standard format that is not expected to change, then it
could simply go into the libtraceevent core.
Thanks,
-- Steve
parent reply other threads:[~2026-05-13 12:51 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CALd=Voi=jdM027HTUL01iRnsShcD+rRj5zbRczEN_y4qZ8QQVA@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260513085145.30dd23e0@fedora \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=lipengfei28@xiaomi.com \
--cc=ljdlns1987@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox