From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Dai, Wei" <wei.dai@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6 0/2] move RSS to flow API
Date: Tue, 9 Jan 2018 07:11:19 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E71ACEAAA6@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180109064430.112576-1-wei.zhao1@intel.com>
> -----Original Message-----
> From: Zhao1, Wei
> Sent: Tuesday, January 9, 2018 2:44 PM
> To: dev@dpdk.org
> Cc: Zhang, Helin
> Subject: [PATCH v6 0/2] move RSS to flow API
>
> The patches mainly finish following functions:
> 1) igb move RSS to flow API
> 2) ixgbe move RSS to flow API
>
> v2:
> -fix bug for RSS flush code.
> -fix patch check warning.
>
> v3:
> -fix bug for ixgbe rss restore.
>
> v4:
> -fix build warning and add release notes comment.
>
> v5:
> -rebase patch set.
>
> v6:
> -rebase patch set.
>
> wei zhao (2):
> net/e1000: move RSS to flow API
> net/ixgbe: move RSS to flow API
>
> doc/guides/rel_notes/release_18_02.rst | 6 ++
> drivers/net/e1000/e1000_ethdev.h | 20 ++++
> drivers/net/e1000/igb_ethdev.c | 17 ++++
> drivers/net/e1000/igb_flow.c | 160
> ++++++++++++++++++++++++++++++++
> drivers/net/e1000/igb_rxtx.c | 61 ++++++++++++
> drivers/net/ixgbe/ixgbe_ethdev.c | 13 +++
> drivers/net/ixgbe/ixgbe_ethdev.h | 10 ++
> drivers/net/ixgbe/ixgbe_flow.c | 165
> +++++++++++++++++++++++++++++++++
> drivers/net/ixgbe/ixgbe_rxtx.c | 65 +++++++++++++
> 9 files changed, 517 insertions(+)
>
> --
> 2.9.3
Applied to dpdk-next-net-intel, with minor commit log changes, thanks!
/Helin
prev parent reply other threads:[~2018-01-09 7:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 9:03 [dpdk-dev] [PATCH 1/2] net/e1000: " Wei Zhao
2017-11-23 9:03 ` [dpdk-dev] [PATCH 2/2] net/ixgbe: " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 0/2] " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 1/2] net/e1000: " Wei Zhao
2017-11-24 3:10 ` [dpdk-dev] [PATCH v2 2/2] net/ixgbe: " Wei Zhao
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 0/2] " Wei Zhao
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 1/2] net/e1000: " Wei Zhao
2017-12-07 9:19 ` Dai, Wei
2017-12-08 2:28 ` Zhao1, Wei
2017-12-21 3:11 ` Zhang, Helin
2018-01-04 8:48 ` Zhao1, Wei
2017-11-24 8:05 ` [dpdk-dev] [PATCH v3 2/2] net/ixgbe: " Wei Zhao
2017-12-07 9:19 ` Dai, Wei
2017-12-08 2:27 ` Zhao1, Wei
2017-12-21 3:11 ` Zhang, Helin
2018-01-04 8:51 ` Zhao1, Wei
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 0/2] " Wei Zhao
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 1/2] net/e1000: " Wei Zhao
2018-01-05 6:05 ` Dai, Wei
2018-01-04 7:46 ` [dpdk-dev] [PATCH v4 2/2] net/ixgbe: " Wei Zhao
2018-01-05 6:01 ` Dai, Wei
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 0/2] " Wei Zhao
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 1/2] net/e1000: " Wei Zhao
2018-01-09 6:20 ` [dpdk-dev] [PATCH v5 2/2] net/ixgbe: " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 0/2] " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 1/2] net/e1000: " Wei Zhao
2018-01-09 6:44 ` [dpdk-dev] [PATCH v6 2/2] net/ixgbe: " Wei Zhao
2018-01-09 7:11 ` Zhang, Helin [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=F35DEAC7BCE34641BA9FAC6BCA4A12E71ACEAAA6@SHSMSX103.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=wei.dai@intel.com \
--cc=wei.zhao1@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).