From: Vipin Varghese <vipin.varghese@intel.com>
To: dev@dpdk.org, john.mcnamara@intel.com, jasvinder.singh@intel.com,
cristian.dumitrescu@intel.com
Cc: amol.patel@intel.com, stephen1.byrne@intel.com,
Vipin Varghese <vipin.varghese@intel.com>
Subject: [dpdk-dev] [PATCH v2] doc/qos_meter: update application information
Date: Tue, 30 Oct 2018 09:26:15 +0530 [thread overview]
Message-ID: <20181030035615.17771-1-vipin.varghese@intel.com> (raw)
In-Reply-To: <20181012140337.22570-1-vipin.varghese@intel.com>
The change adds note for previous colour in colour blind and DROP
in profile table actions. In colour blind mode only valid previous
colour is GREEN. To drop packets based on new colour one needs to
set action as DROP in profile table.
Signed-off-by: Vipin Varghese <vipin.varghese@intel.com>
---
V2:
changed wording from 0 to GREEN - Cristian Dumitrescu
reword the note section - Vipin Varghese
---
doc/guides/sample_app_ug/qos_metering.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/sample_app_ug/qos_metering.rst b/doc/guides/sample_app_ug/qos_metering.rst
index 6391841c6..2e8e0175f 100644
--- a/doc/guides/sample_app_ug/qos_metering.rst
+++ b/doc/guides/sample_app_ug/qos_metering.rst
@@ -149,3 +149,7 @@ 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 GREEN colour is only valid.
+ * To drop the packet, policer_table action has to be set to DROP.
--
2.17.1
prev parent reply other threads:[~2018-10-30 4:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 14:03 [dpdk-dev] [PATCH] " Vipin Varghese
2018-10-15 15:54 ` Dumitrescu, Cristian
2018-10-20 14:10 ` Varghese, Vipin
2018-10-22 9:30 ` Dumitrescu, Cristian
2018-10-30 3:56 ` Vipin Varghese [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181030035615.17771-1-vipin.varghese@intel.com \
--to=vipin.varghese@intel.com \
--cc=amol.patel@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=john.mcnamara@intel.com \
--cc=stephen1.byrne@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).