X-Git-Url: https://gerrit.fd.io/r/gitweb?a=blobdiff_plain;ds=sidebyside;f=src%2Fplugins%2Fmdata%2Fmdata_doc.md;fp=src%2Fplugins%2Fmdata%2Fmdata_doc.md;h=cbbfb01218312f50621bfc5ce6c3a99c740f8c2f;hb=d7b306657d205fddd781e982aec5f3c3dc69fa88;hp=0000000000000000000000000000000000000000;hpb=94afc9391d0588608d67de717a927e9a50349d3a;p=vpp.git

diff --git a/src/plugins/mdata/mdata_doc.md b/src/plugins/mdata/mdata_doc.md
new file mode 100644
index 00000000000..cbbfb012183
--- /dev/null
+++ b/src/plugins/mdata/mdata_doc.md
@@ -0,0 +1,24 @@
+# Buffer metadata change tracker {#mdata_doc}
+
+## Introduction
+
+The mdata plugin uses the vlib main loop "before" performance counter
+hook to snapshoot buffer metadata before calling the node dispatch
+function. Similarly, the plugin uses the main loop "after" hook to
+compare a vectors' worth of buffer metadata after the fact.
+
+The comparison function is a simple octet-by-octet A != B check. We
+accumulate changed octets per-node across the entire run, using a
+single spinlock-protected accumulator.
+
+The "show buffer metadata" command produces a report of all fields
+whose values are changed by nodes visited during a given run.
+
+Since many fields in the vnet_buffer_opaque_t are union members,
+it may appear that a certain node changes numerous fields. The entire
+point of the exercise is to warn developers that if a packet visits
+node N, data placed into opaque union field F *will* be affected.
+
+One should never assume much about buffer metadata immutability across
+arbitrary subgraphs. This tool generates accurate reports, to the
+extent that one exercises the required subgraph trajectories.