THe change adds special note for colour blind and porfile_table
actions. In colour blind mode, the previous colour value is
always 0. For DROP action, one needs to edit the profile_table
entries apporpiately.

Signed-off-by: Vipin Varghese <vipin.vargh...@intel.com>
---
 doc/guides/sample_app_ug/qos_metering.rst | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/doc/guides/sample_app_ug/qos_metering.rst 
b/doc/guides/sample_app_ug/qos_metering.rst
index 6391841c6..1ec94b0b3 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -149,3 +149,8 @@ In this particular case:
 *   Every packet which color has improved is dropped (this particular case 
can't happen, so these values will not be used).
 
 *   For the rest of the cases, the color is changed to red.
+
+
+.. note::
+       * In color blind mode, first row is only valid as previous colour is 0.
+       * To drop the packet, policer_table action has to be set to DROP.
-- 
2.17.1

Reply via email to