From f47122e07e1ecd0151902a3cabe46c60a99bee8e Mon Sep 17 00:00:00 2001 From: Nathan Skrzypczak Date: Fri, 8 Oct 2021 14:05:35 +0200 Subject: docs: convert plugins doc md->rst Type: improvement Change-Id: I7e821cce1feae229e1be4baeed249b9cca658135 Signed-off-by: Nathan Skrzypczak --- src/plugins/mdata/mdata_doc.md | 24 ------------------------ 1 file changed, 24 deletions(-) delete mode 100644 src/plugins/mdata/mdata_doc.md (limited to 'src/plugins/mdata/mdata_doc.md') diff --git a/src/plugins/mdata/mdata_doc.md b/src/plugins/mdata/mdata_doc.md deleted file mode 100644 index cbbfb012183..00000000000 --- a/src/plugins/mdata/mdata_doc.md +++ /dev/null @@ -1,24 +0,0 @@ -# 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. -- cgit 1.2.3-korg