From: John Daley <johndale@cisco.com>
To: ferruh.yigit@intel.com
Cc: dev@dpdk.org, John Daley <johndale@cisco.com>
Subject: [dpdk-dev] [PATCH 3/3] doc: update enic guide for flow API counter action
Date: Thu, 27 Sep 2018 18:58:27 -0700 [thread overview]
Message-ID: <20180928015827.25786-3-johndale@cisco.com> (raw)
In-Reply-To: <20180928015827.25786-1-johndale@cisco.com>
Add counter action support
Signed-off-by: John Daley <johndale@cisco.com>
---
doc/guides/nics/enic.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/nics/enic.rst b/doc/guides/nics/enic.rst
index 438a83d5f..86941fdb2 100644
--- a/doc/guides/nics/enic.rst
+++ b/doc/guides/nics/enic.rst
@@ -260,6 +260,12 @@ Generic Flow API is supported. The baseline support is:
- Selectors: 'is', 'spec' and 'mask'. 'last' is not supported
- In total, up to 64 bytes of mask is allowed across all headers
+- **1400 and later series VICS with advanced filters enabled**
+
+ All the above plus:
+
+ - Action: count
+
More features may be added in future firmware and new versions of the VIC.
Please refer to the release notes.
--
2.16.2
next prev parent reply other threads:[~2018-09-28 1:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 1:58 [dpdk-dev] [PATCH 1/3] net/enic: fix flow API memory leak John Daley
2018-09-28 1:58 ` [dpdk-dev] [PATCH 2/3] net/enic: support for flow counter action John Daley
2018-09-28 1:58 ` John Daley [this message]
2018-09-28 3:08 ` [dpdk-dev] [PATCH v2 1/3] net/enic: fix flow API memory leak John Daley
2018-09-28 3:08 ` [dpdk-dev] [PATCH v2 2/3] net/enic: support for flow counter action John Daley
2018-09-28 3:08 ` [dpdk-dev] [PATCH v2 3/3] doc: update enic guide for flow API " John Daley
2018-10-02 14:49 ` [dpdk-dev] [PATCH v2 1/3] net/enic: fix flow API memory leak Ferruh Yigit
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=20180928015827.25786-3-johndale@cisco.com \
--to=johndale@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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).