From: Zach Brown <zach.brown@oracle.com>
To: karim@opersys.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] tracepipe -- event streams, debugfs, and pipe_buffers
Date: Thu, 20 Jan 2005 15:23:05 -0800 [thread overview]
Message-ID: <41F03D59.3030403@oracle.com> (raw)
In-Reply-To: <41F03CEC.4060207@opersys.com>
Karim Yaghmour wrote:
> 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?
Only briefly. They've always seemed more involved than the sort of
thing I was after. I'll try and sit down and investigate in more detail.
next prev parent reply other threads:[~2005-01-20 23:24 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
2005-01-20 23:23 ` Zach Brown [this message]
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=41F03D59.3030403@oracle.com \
--to=zach.brown@oracle.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.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