From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC/PATCH] ftrace: Allow to change size of function graph filters
Date: Sat, 14 Jan 2017 13:20:00 +0900 [thread overview]
Message-ID: <20170114042000.GA1735@danjae.aot.lge.com> (raw)
In-Reply-To: <20170113111618.53709bf8@gandalf.local.home>
Hi Steve,
On Fri, Jan 13, 2017 at 11:16:18AM -0500, Steven Rostedt wrote:
> On Fri, 13 Jan 2017 13:22:43 +0900
> Namhyung Kim <namhyung@kernel.org> wrote:
>
> > It's currently fixed to 32 and it ignores when user gives a pattern
> > which match to functions more than the size. So filtering like all
> > system calls or many functions with common prefix cannot be set all.
> > Not sure this is right though.
>
> Yes it's small, and there's a reason for it. So I'm giving a
> conditional nack to the patch.
> >
> > This patch adds 'graph_filter_size' file in the tracefs to adjust the
> > size. It can be changed only if the current tracer is not set.
> >
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
>
> The condition is, we need to fix ftrace_graph_addr() first.
>
> for (i = 0; i < ftrace_graph_count; i++) {
>
> That gets called at every function being traced. See where I'm heading
> with that? ;-)
>
> We need to create a hash table or binary search first and make that
> function handle a large ftrace_graph_count before implementing your
> patch. Remove the linear search, replace it with either a binary search
> or a hash. But an O(n) algorithm at every function call is out of the
> question.
Fair enough. I'll try to add a hash table then.
But I'm not sure how to synchronize hash table manipulations. It
seems synchronize_sched() is not good enough for function graph
tracer, right? So I limited changing filter size only when no tracer
is used, but is it ok to have the limitation when adding or removing
an entry to/from the table? If not, what can I do?
Thanks,
Namhyung
next prev parent reply other threads:[~2017-01-14 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-13 4:22 Namhyung Kim
2017-01-13 16:16 ` Steven Rostedt
2017-01-14 4:20 ` Namhyung Kim [this message]
2017-01-14 4:50 ` Steven Rostedt
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=20170114042000.GA1735@danjae.aot.lge.com \
--to=namhyung@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
/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
all inboxes | Powered by JetHome®