DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Dai, Wei" <wei.dai@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 2/2] net/ixgbe: move RSS to flow API
Date: Fri, 5 Jan 2018 06:01:06 +0000	[thread overview]
Message-ID: <49759EB36A64CF4892C1AFEC9231E8D66CF1EC3A@PGSMSX112.gar.corp.intel.com> (raw)
In-Reply-To: <20180104074629.126767-3-wei.zhao1@intel.com>



> -----Original Message-----
> From: Zhao1, Wei
> Sent: Thursday, January 4, 2018 3:46 PM
> To: dev@dpdk.org
> Cc: Dai, Wei <wei.dai@intel.com>; Zhao1, Wei <wei.zhao1@intel.com>
> Subject: [PATCH v4 2/2] net/ixgbe: move RSS to flow API
> 
> Rte_flow actually defined to include RSS, but till now, RSS is out of rte_flow.
> This patch is to move ixgbe existing RSS to rte_flow.
> The old RSS configuration is still reserved.
> 
> Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
Acked-by: Wei Dai <wei.dai@intel.com>

> ---
>  doc/guides/rel_notes/release_18_02.rst |   6 +-
>  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 +++++++++++++
>  5 files changed, 256 insertions(+), 3 deletions(-)
> 

  reply	other threads:[~2018-01-05  6:01 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 [this message]
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           ` [dpdk-dev] [PATCH v6 0/2] " 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=49759EB36A64CF4892C1AFEC9231E8D66CF1EC3A@PGSMSX112.gar.corp.intel.com \
    --to=wei.dai@intel.com \
    --cc=dev@dpdk.org \
    --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).