lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Jesper Derehag via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev <lttng-dev@lists.lttng.org>,
	Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [lttng-dev] Community input: Feedback on use of enumeration type within LTTng-UST
Date: Fri, 29 Jan 2021 15:07:02 +0000	[thread overview]
Message-ID: <AM4PR05MB31530BB10FFB0D30228D46B0DDB99@AM4PR05MB3153.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1389106165.6573.1611674358449.JavaMail.zimbra@efficios.com>

Hi,

I dont have any data regarding enum usage unfortunatly.

But is it possible to share metadata between multiple tp-providers?
If so, would you not be required anyway to re-generate the enumeration labels given that any trace producer (sharing the same metadata) may have different enumeration definitions?
For example if you would lets say trace different versions of the same app but where the enum definition have changed?
Cases like those I guess would force you to atleast version enum labels or somesuch?

/Jesper

________________________________________
Från: lttng-dev <lttng-dev-bounces@lists.lttng.org> för Mathieu Desnoyers via lttng-dev <lttng-dev@lists.lttng.org>
Skickat: den 26 januari 2021 16:19
Till: lttng-dev
Ämne: [lttng-dev] Community input: Feedback on use of enumeration type within LTTng-UST

Hi,

We are currently working on the CTF2 specification [1] at EfficiOS, and there is
a user metric we would need to help us with a design decision with respect
to enumerations. This is where we would need community input.

The usage metrics in question are with respect to LTTng-UST enumeration types
(TRACEPOINT_ENUM) [2] used by tracepoint events within instrumented applications.

A tracepoint enumeration can be used by many events. What we are looking for is to get
an idea of the common use, and extreme cases as well.

Ideally, what we would need is:

- For each enumeration within your application instrumentation (TRACEPOINT_ENUM), how
  many events refer to each enumeration ? (average, mode, and maximum)
- For each TRACEPOINT_ENUM, how many labels do they possess ? (sum number of
  ctf_enum_value/ctf_enum_range/ctf_enum_auto entries) (average, mode, and maximum)
- For each TRACEPOINT_ENUM, for each label, what is the string length ? (average, mode, and maximum)

Based on this information, we can estimate the data overhead generated by repeating enumeration
labels in the LTTng-UST metadata. We need to decide whether we allow references to a single
enumeration description when it is used by many events, or if we require repeatedly serializing
the entire enumeration description for each event field using the enumeration.

Thanks,

Mathieu

[1] https://lists.lttng.org/pipermail/lttng-dev/2020-November/029777.html
[2] https://lttng.org/man/3/lttng-ust/v2.12/#doc-tracepoint-enum

--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  reply	other threads:[~2021-01-29 15:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 15:19 [lttng-dev] Community input: Feedback on use of enumeration type within LTTng-UST Mathieu Desnoyers via lttng-dev
2021-01-29 15:07 ` Jesper Derehag via lttng-dev [this message]
2021-02-09 21:26   ` Mathieu Desnoyers via lttng-dev

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=AM4PR05MB31530BB10FFB0D30228D46B0DDB99@AM4PR05MB3153.eurprd05.prod.outlook.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=jderehag@hotmail.com \
    --cc=mathieu.desnoyers@efficios.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).