X-Git-Url: https://git.liburcu.org/?a=blobdiff_plain;f=2.12%2Flttng-docs-2.12.txt;h=4b879478158f6ee3ad11e39a80eb9a646d8085aa;hb=3cd5f5046bca14706abaa8362af9741f9a86128f;hp=d80ba3057249f04637d3311265deb8c29d5ee8b8;hpb=489967cfd5d44bf6a386f672e5093c949470491c;p=lttng-docs.git

diff --git a/2.12/lttng-docs-2.12.txt b/2.12/lttng-docs-2.12.txt
index d80ba30..4b87947 100644
--- a/2.12/lttng-docs-2.12.txt
+++ b/2.12/lttng-docs-2.12.txt
@@ -1441,11 +1441,11 @@ LTTng can send the generated trace data to different locations. The
 _tracing session mode_ dictates where to send it. The following modes
 are available in LTTng{nbsp}{revision}:
 
-Local mode::
+[[local-mode]]Local mode::
   LTTng writes the traces to the file system of the machine it traces
   (target system).
 
-Network streaming mode::
+[[net-streaming-mode]]Network streaming mode::
   LTTng sends the traces over the network to a
   <<lttng-relayd,relay daemon>> running on a remote system.
 
@@ -1457,7 +1457,7 @@ that is, a copy of the current sub-buffers of the tracing session, and
 to write it to the file system of the target or to send it over the
 network to a <<lttng-relayd,relay daemon>> running on a remote system.
 
-Live mode::
+[[live-mode]]Live mode::
   This mode is similar to the network streaming mode, but a live
   trace viewer can connect to the distant relay daemon to
   <<lttng-live,view event records as LTTng generates them>>.
@@ -1615,14 +1615,18 @@ discard mode, the tracer only discards the event record that doesn't
 fit.
 
 In discard mode, LTTng increments a count of lost event records when an
-event record is lost and saves this count to the trace. In overwrite
-mode, since LTTng{nbsp}2.8, LTTng increments a count of lost sub-buffers
-when a sub-buffer is lost and saves this count to the trace. In this
-mode, LTTng doesn't write to the trace the exact number of lost event
-records in those lost sub-buffers. Trace analyses can use saved
-discarded event record and sub-buffer counts of the trace to decide
-whether or not to perform the analyses even if trace data is known to be
-missing.
+event record is lost and saves this count to the trace. Since
+LTTng{nbsp}2.8, in overwrite mode, LTTng writes to a given sub-buffer
+its sequence number within its data stream. With a <<local-mode,local>>,
+<<net-streaming-mode,network streaming>>, or <<live-mode,live>>
+<<tracing-session,tracing session>>, a trace reader can use such
+sequence numbers to report lost packets. In overwrite mode, LTTng
+doesn't write to the trace the exact number of lost event records in
+those lost sub-buffers.
+
+Trace analyses can use saved discarded event record and sub-buffer
+(packet) counts of the trace to decide whether or not to perform the
+analyses even if trace data is known to be missing.
 
 There are a few ways to decrease your probability of losing event
 records.