From: Jon Masters <jonathan@jonmasters.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [tracing] ring_buffer question
Date: Sun, 17 May 2009 17:08:25 -0400 [thread overview]
Message-ID: <1242594505.6327.3.camel@localhost.localdomain> (raw)
Steven,
Is there any reason you can think of why we don't just generalize
kernel/trace/ring_buffer into kernel/ring_buffer, remove the static
per_cpu buffer allocation and have this available for non-tracing?
As it is, trace buffers only store generic data and the design (swap on
read) is very nicely done for many other ring buffer uses.
Jon.
next reply other threads:[~2009-05-17 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-17 21:08 Jon Masters [this message]
2009-05-18 0:39 ` [tracing] ring_buffer question Jon Masters
2009-05-18 15:58 ` David Smith
2009-05-18 16:23 ` Steven Rostedt
2009-05-18 16:52 ` David Smith
2009-05-18 17:03 ` 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=1242594505.6327.3.camel@localhost.localdomain \
--to=jonathan@jonmasters.org \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.