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, Wei Zhao <wei.zhao1@intel.com>
Subject: [dpdk-dev] [PATCH] doc: add queue region feature info to release notes
Date: Thu, 21 Dec 2017 11:52:00 +0800	[thread overview]
Message-ID: <20171221035200.22479-1-wei.zhao1@intel.com> (raw)

This patch add inforation about i40e queue region
realted to release notes, it has been missed before.

Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
---
 doc/guides/rel_notes/release_17_11.rst | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 016a08c..4b59027 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -210,6 +210,23 @@ New Features
 
   Updated ixgbe ethernet PMD to support ``rte_security`` inline IPSec offload.
 
+* **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 to different queues in
+  different queue regions.
+
+* **Added the testpmd app to support queue region configuration with CLI.**
+
+  This patch add a API configuration of queue region in rss with command line.
+  It can parse the parameters of region index, queue number,
+  queue start index, user priority, traffic classes and so on.
+  According to commands from command line, it will call i40e
+  private API and start the process of set or flush queue region
+  configure. As this feature is specific for i40e, so private API
+  will be used. Aslo add a document for these new commands.
+
 * **Updated ipsec-secgw application to support rte_security.**
 
   Updated the ``ipsec-secgw`` sample application to support ``rte_security``
-- 
2.9.3

             reply	other threads:[~2017-12-21  3:59 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-21  3:52 Wei Zhao [this message]
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       ` [dpdk-dev] [PATCH v5] " Wei Zhao
2018-01-23 10:22         ` 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=20171221035200.22479-1-wei.zhao1@intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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).