Return-Path: DKIM-Filter: OpenDKIM Filter v2.10.3 mail.efficios.com 9A82627F723 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=efficios.com; s=default; t=1588100085; bh=9M1SVm5+5pGopEz6Ft3YuHTsU88dlkyoGBasOSOiR7g=; h=Date:From:To:Message-ID:MIME-Version; b=DYgwhLZ8Ii8M1MprsMuJxBPuAc/wCuTZrmy3N4y3/2N1Xi2OmsL80LLCFwCgufdmX n2TAipZ22LdcUc86q89RBQGoeA6IltM5xMJj2xGwXYHH5EgqAoXq3jPHUSbFX5Znik 7oPf8+BdJ8IfjMwUb5cE4K2tZfCscJmwptpV3nJH50xiihpBgnVfwcnJ1QoiA5zEAD Ko5OOAd+7HP0j3ZIH+VMtu/vT5pupTzjXTNp+n++TrUb0y5OhYgv4uFSEBrundJ9fv mcVhY93nluyMnLt9hk8BxE0XJM79GK1xQwubRTvBupcIBDyhepI/4Ro+AFqtChqSeq jpvJhykVWKlmA== Date: Tue, 28 Apr 2020 14:54:45 -0400 (EDT) From: Mathieu Desnoyers Message-ID: <252145848.72946.1588100085527.JavaMail.zimbra@efficios.com> In-Reply-To: <1480394831.72907.1588099321783.JavaMail.zimbra@efficios.com> References: <20200423205226.496-1-mathieu.desnoyers@efficios.com> <20200423205226.496-3-mathieu.desnoyers@efficios.com> <1480394831.72907.1588099321783.JavaMail.zimbra@efficios.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [diamon-discuss] [RFC PATCH CTF 2/3] Clarify monotonicity requirement on timestamp begin List-Id: DiaMon diagnostic and monitoring workgroup general discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Philippe Proulx Cc: Diamon discuss , lttng-dev , Jeremie Galarneau , Genevieve Bastien ----- On Apr 28, 2020, at 2:42 PM, Philippe Proulx pproulx@efficios.com wrote: > ----- Original Message ----- >> From: "Mathieu Desnoyers" >> To: "gbastien+lttng" , "Matthew Khouzam" >> , >> diamon-discuss@linuxfoundation.org, pproulx@efficios.com, "Jeremie Galarneau" >> >> Cc: "lttng-dev" , "Mathieu Desnoyers" >> >> Sent: Thursday, 23 April, 2020 16:52:25 >> Subject: [RFC PATCH CTF 2/3] Clarify monotonicity requirement on timestamp begin > >> Signed-off-by: Mathieu Desnoyers >> --- >> common-trace-format-specification.md | 10 ++++++---- >> 1 file changed, 6 insertions(+), 4 deletions(-) >> >> diff --git a/common-trace-format-specification.md >> b/common-trace-format-specification.md >> index f5fea51..53b70f4 100644 >> --- a/common-trace-format-specification.md >> +++ b/common-trace-format-specification.md >> @@ -836,10 +836,12 @@ TSDL metadata): >> range between these timestamps should include all event timestamps >> assigned to events contained within the packet. The timestamp at the >> beginning of an event packet is guaranteed to be below or equal the >> - timestamp at the end of that event packet. The timestamp at the end >> - of an event packet is guaranteed to be below or equal the >> - timestamps at the end of any following packet within the same stream. >> - See [Clocks](#spec8) for more detail. >> + timestamp at the end of that event packet. The timestamp at the >> + beginning of an event packet is guaranteed to be above or equal the > > "greater than or equal to" done > >> + timestamps at the beginning of any prior packet within the same >> + stream. The timestamp at the end of an event packet is guaranteed to >> + be below or equal the timestamps at the end of any following packet > > "less than or equal to" done, Thanks! Mathieu > > Phil > >> + within the same stream. See [Clocks](#spec8) for more detail. >> * **Events discarded count**. Snapshot of a per-stream >> free-running counter, counting the number of events discarded that >> were supposed to be written in the stream after the last event in >> -- > > 2.11.0 -- Mathieu Desnoyers EfficiOS Inc. http://www.efficios.com