From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id pKaFBz/uIGIsXgAAWB0awg (envelope-from ) for ; Thu, 03 Mar 2022 11:35:11 -0500 Received: by simark.ca (Postfix, from userid 112) id 0E6C21F3CA; Thu, 3 Mar 2022 11:35:11 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HTML_MESSAGE,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from lists.lttng.org (lists.lttng.org [167.114.26.123]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 6E46F1EA69 for ; Thu, 3 Mar 2022 11:35:10 -0500 (EST) Received: from lists-lttng01.efficios.com (localhost [IPv6:::1]) by lists.lttng.org (Postfix) with ESMTP id 4K8c656Gb8z6k3; Thu, 3 Mar 2022 11:35:09 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=lists.lttng.org; s=default; t=1646325310; bh=IyjUg1MESWUF8hvgBbaD+7d2ocWRDZJRiDruGI6Hjd0=; h=Date:To:Subject:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=yjzurMJxvexnea+ORuA3U2ColvsCUajMGcrKM349O/dEqEW2sTPu/giBhvkGZp8wc r3HYIVD5vFStJdo6R+esfE2LAPHz2iYMOFLRMr9ZovkE2ZM+CoQ2OiiXXWbkUYP4BS 80SdSybS3Kppgg033fk7ZL8zorUKkp9Ue8lC14BGKVkI8HfVAXL4CW5Yz7hHS1WYTI WN2rZcBpdEM6FzuMftC/qtqAGsH1ODBuNS16eBTPz0ONjCyN2RYn5tz24v/6vuq2X+ Yb3MpqGqZZWO8cOnV6OYrttbKu1LDSaH3X+wUNXWzm6WAdllRUrF422xyqu/wKKYPK W1444b3hB8xAw== Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by lists.lttng.org (Postfix) with ESMTPS id 4K8c6422f0z6k2 for ; Thu, 3 Mar 2022 11:35:08 -0500 (EST) Received: by mail-wr1-x42a.google.com with SMTP id ay10so8707378wrb.6 for ; Thu, 03 Mar 2022 08:35:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zWiKneF4dFWBGb7GE1i/ib5yFnoe7bBYAgKWEOSJBDs=; b=imDiRNfqHLkXzryF/qevHh3XI4+vklrNZahCtqk5ecLICofmjFVULGgB9I6IaPiwoS locaNrLk/8fLBFJay/S1AvpGKaufHHp+TYxrhYtm2TSEBiPD7JI7tQqmXPyVKvrL8FLF mWRPBqMZqXA9X9O4RyBIij881r9lsQ4XtziUsQh2bNsq2Q7r+Z3dsW5CIbsaAlQzBhbz sz5hM22LSdByshz0SdXAJF3gFyfyUG2SV/AvZEPh9QYgs1ZKGOW59jhZi5c2XDitqG1M F2EblA96STjfSpjh+8fS0I3cuFRlj1zk92NyKJrpkHJS5NcNNlueWFdfM5eV6b10HzF1 ls6g== X-Gm-Message-State: AOAM530uuC+N8yh6HrJptSkOymmtUTmb1RtGlvqT2bKLG0fbdYAbua+i l31iLmSbGSNSfso6fkvXo+ZNhjBURI/lMLfVhqB2HdmYz1Y= X-Google-Smtp-Source: ABdhPJzcsOIgUCcbLCI6L5pfAU66DBHWuKm3bdsY2eMrrisKtO/biqBZUM7wwlEFyit4hkR/D6PdCrikuAU9UJq2U4w= X-Received: by 2002:a5d:47a5:0:b0:1e8:88b3:16b7 with SMTP id 5-20020a5d47a5000000b001e888b316b7mr27901494wrb.417.1646325306521; Thu, 03 Mar 2022 08:35:06 -0800 (PST) MIME-Version: 1.0 Date: Thu, 3 Mar 2022 08:34:55 -0800 Message-ID: To: lttng-dev@lists.lttng.org Subject: [lttng-dev] [barectf] Is it possible to include a packet sequence count? X-BeenThere: lttng-dev@lists.lttng.org X-Mailman-Version: 2.1.39 Precedence: list List-Id: LTTng development list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Jon Lamb via lttng-dev Reply-To: Jon Lamb Content-Type: multipart/mixed; boundary="===============9039425098044307516==" Errors-To: lttng-dev-bounces@lists.lttng.org Sender: "lttng-dev" --===============9039425098044307516== Content-Type: multipart/alternative; boundary="0000000000001479da05d952fb6e" --0000000000001479da05d952fb6e Content-Type: text/plain; charset="UTF-8" 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 --0000000000001479da05d952fb6e Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

Looking through the docs u= nder packet features, it doesn't look like including a packet_seq_num i= s supported.
If I didn't overlook the docs, is this a feature that w= ould 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 wo= rkaround, but it appears to be a reserved field type member name.

Be= st,
Jon
--0000000000001479da05d952fb6e-- --===============9039425098044307516== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ lttng-dev mailing list lttng-dev@lists.lttng.org https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev --===============9039425098044307516==--