From: michel.dagenais@polymtl.ca (Michel Dagenais)
Subject: [ltt-dev] UST socket protocol
Date: Tue, 07 Sep 2010 09:24:05 -0400 [thread overview]
Message-ID: <4C863CF5.5050705@polymtl.ca> (raw)
In-Reply-To: <alpine.DEB.2.00.1009070823470.16298@as68123.uab.ericsson.se>
> I've been looking through the socket protocol for UST and am a bit
> curious about the construction of it. Is there a reason we haven't just
> defined a ustctl package type with a command field, a result field and a
> data field?
>
> This would reduce the amount of scanning required by quite a bit.
I have not looked closely at the protocol. Reusing an existing protocol
would make sense. For instance, reusing the GDB protocol could be
interesting since GDB is already capable of listing and activating UST
tracepoints. Moreover, the GDB protocol is also used by kgdb to enable
kernel dynamic tracepoints with kprobes with a recent patch. I doubt
that the GDB protocol would be optimized for fast transfers of tracing
data, but that may be transmitted through a separate channel.
The TCF protocol could be another candidate.
next prev parent reply other threads:[~2010-09-07 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 6:30 Nils Carlson
2010-09-07 13:24 ` Michel Dagenais [this message]
2010-09-09 7:27 ` Pierre-Marc Fournier
2010-09-09 15:45 ` Nils Carlson
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=4C863CF5.5050705@polymtl.ca \
--to=michel.dagenais@polymtl.ca \
/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