From: Steven Rostedt <rostedt@goodmis.org>
To: Namhyung Kim <namhyung@kernel.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: Fri, 13 Jan 2017 11:16:18 -0500 [thread overview]
Message-ID: <20170113111618.53709bf8@gandalf.local.home> (raw)
In-Reply-To: <20170113042243.15259-1-namhyung@kernel.org>
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.
Thanks!
-- Steve
next prev parent reply other threads:[~2017-01-13 16:16 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 [this message]
2017-01-14 4:20 ` Namhyung Kim
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=20170113111618.53709bf8@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.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®