DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wei Zhao <wei.zhao1@intel.com>
To: dev@dpdk.org
Cc: john.mcnamara@intel.com, thomas@monjalon.net, stable@dpdk.org,
	Wei Zhao <wei.zhao1@intel.com>
Subject: [dpdk-dev] [PATCH v5] doc: add queue region feature info to release notes
Date: Mon, 22 Jan 2018 13:18:30 +0800	[thread overview]
Message-ID: <20180122051830.102203-1-wei.zhao1@intel.com> (raw)
In-Reply-To: <20180119032814.57248-1-wei.zhao1@intel.com>

This patch add inforation about i40e queue region
realted to release notes, it has been missed before
in v17.11 release notes. This feature has been
implemented in v17.11.

Signed-off-by: Wei Zhao <wei.zhao1@intel.com>

---

v2:
-change this information to v18.02 release notes.

v3:
-rework it on dpdk-next-net-intel sub tree.

v4:
-rework it into 17.11 release notes and i40e.rst.

v5:
-change some use of words and comment location in file.
---
 doc/guides/nics/i40e.rst               | 25 ++++++++++++++++++++++++-
 doc/guides/rel_notes/release_17_11.rst |  7 +++++++
 2 files changed, 31 insertions(+), 1 deletion(-)

diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst
index 50d5e36..29601f1 100644
--- a/doc/guides/nics/i40e.rst
+++ b/doc/guides/nics/i40e.rst
@@ -66,7 +66,7 @@ Features of the I40E PMD are:
 - IEEE1588/802.1AS timestamping
 - VF Daemon (VFD) - EXPERIMENTAL
 - Dynamic Device Personalization (DDP)
-
+- Queue region configuration
 
 Prerequisites
 -------------
@@ -430,6 +430,29 @@ For example, to use only 48bit prefix for IPv6 src address for IPv6 TCP RSS:
    testpmd> port config 0 pctype 43 hash_inset set field 14
    testpmd> port config 0 pctype 43 hash_inset set field 15
 
+Queue region configuration
+~~~~~~~~~~~~~~~~~~~~~~~~~~~
+The Ethernet Controller X710/XL710 supports a feature of queue regions
+configuration for RSS in the PF, so that different traffic classes or
+different packet classification types can be separated to different
+queues in different queue regions. There is an API for configuration
+of queue regions in RSS with a command line. It can parse the parameters
+of the region index, queue number, queue start index, user priority, traffic
+classes and so on. Depending on commands from the command line, it will call
+i40e private APIs and start the process of setting or flushing the queue
+region configuration. As this feature is specific for i40e only private
+APIs are used. These new ``test_pmd`` commands are as shown below. For
+details please refer to :doc:`../testpmd_app_ug/index`.
+
+.. code-block:: console
+
+   testpmd> set port (port_id) queue-region region_id (value) \
+		queue_start_index (value) queue_num (value)
+   testpmd> set port (port_id) queue-region region_id (value) flowtype (value)
+   testpmd> set port (port_id) queue-region UP (value) region_id (value)
+   testpmd> set port (port_id) queue-region flush (on|off)
+   testpmd> show port (port_id) queue-region
+
 Limitations or Known issues
 ---------------------------
 
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index c37c71a..088778b 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -216,6 +216,13 @@ New Features
   profiles which can be programmed by dynamic device personalization (DDP)
   process.
 
+* **Added the i40e ethernet driver to support queue region feature.**
+
+  This feature enable queue regions configuration for RSS in PF,
+  so that different traffic classes or different packet
+  classification types can be separated into different queues in
+  different queue regions.
+
 * **Updated ipsec-secgw application to support rte_security.**
 
   Updated the ``ipsec-secgw`` sample application to support ``rte_security``
-- 
2.9.3

  parent reply	other threads:[~2018-01-22  5:26 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  3:52 [dpdk-dev] [PATCH] " Wei Zhao
2017-12-21 18:10 ` Ferruh Yigit
2017-12-22  1:36   ` Zhao1, Wei
2017-12-22  3:25     ` Ferruh Yigit
2017-12-22  3:52       ` Zhao1, Wei
2018-01-16 11:27   ` Thomas Monjalon
2018-01-16 11:49     ` Ferruh Yigit
2018-01-16 16:01       ` Ferruh Yigit
2018-01-16 17:35         ` Thomas Monjalon
2018-01-03  8:13 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-01-07 15:51   ` Zhang, Helin
2018-01-08  1:56     ` Zhao1, Wei
2018-01-08  3:39   ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-01-09  6:15     ` Zhang, Helin
2018-01-09  6:17     ` Zhang, Helin
2018-01-09  6:18       ` Zhao1, Wei
2018-01-09  6:26     ` Zhang, Helin
2018-01-09  6:29     ` Zhang, Helin
2018-01-16 21:53       ` Thomas Monjalon
2018-01-18  2:00         ` Zhao1, Wei
2018-01-18  7:30           ` Thomas Monjalon
2018-01-19  3:15             ` Zhao1, Wei
2018-01-19  9:13               ` Thomas Monjalon
2018-01-19  9:17                 ` Thomas Monjalon
2018-01-22  1:58                   ` Zhao1, Wei
2018-01-22  5:30                   ` Zhao1, Wei
2018-01-19  3:38             ` Zhao1, Wei
2018-01-18  3:45     ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-01-19  3:28     ` Wei Zhao
2018-01-21 21:22       ` Mcnamara, John
2018-01-22  5:27         ` Zhao1, Wei
2018-01-22  5:18       ` Wei Zhao [this message]
2018-01-23 10:22         ` [dpdk-dev] [PATCH v5] " Mcnamara, John
2018-01-23 15:01           ` Zhang, Helin

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=20180122051830.102203-1-wei.zhao1@intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).