From 6a7c61df4c4610004973ce0cff21fc72d8969de5 Mon Sep 17 00:00:00 2001 From: Mathieu Desnoyers Date: Thu, 5 May 2011 18:34:31 -0400 Subject: [PATCH] Explain that content size and packet size are opt. Signed-off-by: Mathieu Desnoyers --- common-trace-format-proposal.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/common-trace-format-proposal.txt b/common-trace-format-proposal.txt index efd780f..0e57046 100644 --- a/common-trace-format-proposal.txt +++ b/common-trace-format-proposal.txt @@ -604,8 +604,9 @@ don't need to declare a "stream_id" field. 5.2 Event Packet Context Description Event packet context example. These are declared within the stream declaration -in the metadata. All these fields are optional except for "content_size" and -"packet_size", which must be present in the context. +in the metadata. All these fields are optional. If the packet size field is +missing, the whole stream only contains a single packet. If the content +size field is missing, the packet is filled (no padding). An example event packet context type: -- 2.34.1