From: Frederic Weisbecker <fweisbec@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Li Zefan <lizf@cn.fujitsu.com>, Jason Baron <jbaron@redhat.com>,
Masami Hiramatsu <mhiramat@redhat.com>
Subject: Re: [PATCH 2/2] tracing: Allocate the ftrace event profile buffer dynamically
Date: Fri, 18 Sep 2009 04:23:27 +0200 [thread overview]
Message-ID: <20090918022325.GA5310@nowhere> (raw)
In-Reply-To: <1253240103.20020.253.camel@gandalf.stny.rr.com>
On Thu, Sep 17, 2009 at 10:15:03PM -0400, Steven Rostedt wrote:
>
> Is this allocating a buffer for every event? Why not just have one? All
> events can share the same buffer. It's only a temp buffer, and can only
> be used by one event at a time per cpu.
>
> -- Steve
>
Oh you're right. That was so obvious though...
The v2 is coming soon.
Thanks.
next prev parent reply other threads:[~2009-09-18 2:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 1:33 [PATCH 0/2] tracing: Tracing event profiling updates Frederic Weisbecker
2009-09-18 1:33 ` [PATCH 1/2] tracing: Factorize the events profile accounting Frederic Weisbecker
2009-09-18 2:15 ` Steven Rostedt
2009-09-18 3:45 ` Li Zefan
2009-09-18 1:33 ` [PATCH 2/2] tracing: Allocate the ftrace event profile buffer dynamically Frederic Weisbecker
2009-09-18 2:15 ` Steven Rostedt
2009-09-18 2:23 ` Frederic Weisbecker [this message]
2009-09-18 4:24 ` [PATCH 0/2 v2] tracing: Tracing event profiling updates Frederic Weisbecker
2009-09-18 5:36 ` [PATCH 0/2 v3] " Frederic Weisbecker
2009-09-19 7:34 ` Ingo Molnar
2009-09-19 8:03 ` Frederic Weisbecker
2009-09-18 5:36 ` [PATCH 2/2 v3] tracing: Allocate the ftrace event profile buffer dynamically Frederic Weisbecker
2009-09-18 4:24 ` [PATCH 1/2] tracing: Factorize the events profile accounting Frederic Weisbecker
2009-09-18 4:24 ` [PATCH 2/2] tracing: Allocate the ftrace event profile buffer dynamically Frederic Weisbecker
2009-09-18 4:31 ` Frederic Weisbecker
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=20090918022325.GA5310@nowhere \
--to=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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