Explain that content size and packet size are opt.
authorMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 5 May 2011 22:34:31 +0000 (18:34 -0400)
committerMathieu Desnoyers <mathieu.desnoyers@efficios.com>
Thu, 5 May 2011 22:34:31 +0000 (18:34 -0400)
Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
common-trace-format-proposal.txt

index efd780f3d4d3d743593f3f4a32fbf806aad8b093..0e5704657e46bd68e86ae3fc3f0d861a95cf0133 100644 (file)
@@ -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:
 
This page took 0.031111 seconds and 4 git commands to generate.