Update: packet context sizes expressed in bits

The rest of the specification express sizes in bits rather than bytes.
The Babeltrace and LTTng reference implementations use bits rather than
bytes for the packet context content_size and packet_size fields.

Standardizing on bits rather than bytes makes the specification more
consistent.

Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>

diff --git a/common-trace-format-specification.txt b/common-trace-format-specification.txt
index b924b6f22657ea5d5cdd78a204b5f22492deaf08..d0636cfba4dc7987e6cccd6a7847d798d309cc79 100644 (file)
--- a/common-trace-format-specification.txt
+++ b/common-trace-format-specification.txt
@@ -1,4 +1,4 @@
-Common Trace Format (CTF) Specification (v1.7)
+Common Trace Format (CTF) Specification (pre-v1.8)
 
 Mathieu Desnoyers, EfficiOS Inc.
 
@@ -662,8 +662,8 @@ Event packet header (all fields are optional, specified by TSDL meta-data):
 
 Event packet context (all fields are optional, specified by TSDL meta-data):
 
-- Event packet content size (in bytes).
-- Event packet size (in bytes, includes padding).
+- Event packet content size (in bits).
+- Event packet size (in bits, includes padding).
 - Event packet content checksum. Checksum excludes the event packet
   header.
 - Per-stream event packet sequence count (to deal with UDP packet loss). The