DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
	"Mcnamara, John" <john.mcnamara@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] doc: add queue region feature info to release	notes
Date: Mon, 8 Jan 2018 01:56:26 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07C94DE1@PGSMSX103.gar.corp.intel.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E71ACE5E14@SHSMSX103.ccr.corp.intel.com>

Hi, helin

> -----Original Message-----
> From: Zhang, Helin
> Sent: Sunday, January 7, 2018 11:52 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; Mcnamara, John
> <john.mcnamara@intel.com>
> Cc: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Subject: RE: [dpdk-dev] [PATCH v2] doc: add queue region feature info to
> release notes
> 
> Hi John
> 
> Could you help to review with ACK or comments? :)
> 
> Hi Wei
> 
> 'Git am' failure is as below. Please fix it on dpdk-next-net-intel sub tree.
> Thanks!
> 

Ok, I will updated later.


> Description: [dpdk-dev,v2] doc: add queue region feature info to release
> notes
> Applying: doc: add queue region feature info to release notes
> error: patch failed: doc/guides/rel_notes/release_18_02.rst:41
> error: doc/guides/rel_notes/release_18_02.rst: patch does not apply Patch
> failed at 0001 doc: add queue region feature info to release notes
> 
> Regards,
> Helin
> 
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wei Zhao
> > Sent: Wednesday, January 3, 2018 4:13 PM
> > To: dev@dpdk.org
> > Cc: Mcnamara, John; Zhao1, Wei
> > Subject: [dpdk-dev] [PATCH v2] doc: add queue region feature info to
> > release notes
> I'd suggest to use 'update release notes with queue region feature'
> >
> > 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.
> This patch updates the releases notes with queue region feature which was
> enabled in 17.11 in silence.
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> >
> > ---
> >
> > v2:
> > -change this information to v18.02 release notes.
> > ---
> >  doc/guides/rel_notes/release_18_02.rst | 17 +++++++++++++++++
> >  1 file changed, 17 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/release_18_02.rst
> > b/doc/guides/rel_notes/release_18_02.rst
> > index 24b67bb..0e9f17b 100644
> > --- a/doc/guides/rel_notes/release_18_02.rst
> > +++ b/doc/guides/rel_notes/release_18_02.rst
> > @@ -41,6 +41,23 @@ New Features
> >       Also, make sure to start the actual text at the margin.
> >
> =========================================================
> >
> > +* **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. This feature has been implemented in v17.11.
> > +
> > +* **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.
> > +  This feature has been implemented in v17.11.
> >
> >  API Changes
> >  -----------
> > --
> > 2.9.3

  reply	other threads:[~2018-01-08  1:56 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 [this message]
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=A2573D2ACFCADC41BB3BE09C6DE313CA07C94DE1@PGSMSX103.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=helin.zhang@intel.com \
    --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).