From: Karim Yaghmour <karim@opersys.com>
To: Zach Brown <zach.brown@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] tracepipe -- event streams, debugfs, and pipe_buffers
Date: Thu, 20 Jan 2005 18:21:16 -0500 [thread overview]
Message-ID: <41F03CEC.4060207@opersys.com> (raw)
In-Reply-To: <41F0344C.1030404@oracle.com>
Zach Brown wrote:
> Thoughts? I, for one, am tired of writing throw-away per-cpu tracing
> patches ;)
Have you taken a look at relayfs and ltt?
Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546
next prev parent reply other threads:[~2005-01-20 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-20 22:44 [RFC] tracepipe -- event streams, debugfs, and pipe_buffers Zach Brown
2005-01-20 23:21 ` Karim Yaghmour [this message]
2005-01-20 23:23 ` Zach Brown
2005-01-21 3:09 ` Karim Yaghmour
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=41F03CEC.4060207@opersys.com \
--to=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.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 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.