From: Jon Lamb via lttng-dev <lttng-dev@lists.lttng.org>
To: lttng-dev@lists.lttng.org
Subject: [lttng-dev] [barectf] Is it possible to include a packet sequence count?
Date: Thu, 3 Mar 2022 08:34:55 -0800 [thread overview]
Message-ID: <CAJMh_qV01v9X=Nos2za8hbQdLvXgG5J=ZYiE3_OPOP5A5SQ-Lw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 530 bytes --]
Hi,
Looking through the docs under packet features, it doesn't look like
including a packet_seq_num is supported.
If I didn't overlook the docs, is this a feature that would be considered
given that it's called out in the spec?
It'd be really handy to have this in the CTF packet rather than having to
manage it elsewhere.
I thought I could manage this in my platform impl by adding packet_seq_num
to my packet-context-field-type-extra-members as a workaround, but it
appears to be a reserved field type member name.
Best,
Jon
[-- Attachment #1.2: Type: text/html, Size: 694 bytes --]
[-- Attachment #2: Type: text/plain, Size: 156 bytes --]
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
reply other threads:[~2022-03-03 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJMh_qV01v9X=Nos2za8hbQdLvXgG5J=ZYiE3_OPOP5A5SQ-Lw@mail.gmail.com' \
--to=lttng-dev@lists.lttng.org \
--cc=lamb.jon.io@gmail.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 read-only IMAP folder(s) and NNTP newsgroup(s).