DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Wu, Jingjing" <jingjing.wu@intel.com>
To: "Chilikin, Andrey" <andrey.chilikin@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Support for flow director behavior	"passthru" on Intel FVL NIC
Date: Mon, 19 Oct 2015 01:51:52 +0000	[thread overview]
Message-ID: <9BB6961774997848B5B42BEC655768F8D031E2@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <1443620583-28310-1-git-send-email-andrey.chilikin@intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Andrey Chilikin
> Sent: Wednesday, September 30, 2015 9:43 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 0/3] Support for flow director behavior
> "passthru" on Intel FVL NIC
> 
> This patch set adds new flow director behavior "passthru" on Intel X(L)710
> NIC.
> When this mode is selected flow director will direct packet to LAN while the
> queue is defined by other filters. This can be used to extract flexible payload
> to RX desriptor with the flow director filter while targeted queue will be
> defined by other filters, for example, by hash filter (RSS).
> 
> v2: rename RTE_ETH_FDIR_OTHER to RTE_ETH_FDIR_PASSTHRU
> 
> Andrey Chilikin (3):
>   librte_ether: add RTE_ETH_FDIR_PASSTHRU for flow director behavior
>   i40e: add RTE_ETH_FDIR_PASSTHRU processing for flow director behavior
>   ixgbe: add check for supported flow director behaviors
> 
>  drivers/net/i40e/i40e_fdir.c    |   12 ++++++++++--
>  drivers/net/ixgbe/ixgbe_fdir.c  |    3 ++-
>  lib/librte_ether/rte_eth_ctrl.h |    1 +
>  3 files changed, 13 insertions(+), 3 deletions(-)
> 
> --
Acked-by: Jingjing Wu <jingjing.wu@intel.com>

> 1.7.4.1

  parent reply	other threads:[~2015-10-19  1:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-29 14:26 [dpdk-dev] [PATCH 0/3] Support for flow director behavior "other" " Andrey Chilikin
2015-09-29 14:26 ` [dpdk-dev] [PATCH 1/3] librte_ether: add RTE_ETH_FDIR_OTHER for flow director behavior Andrey Chilikin
2015-09-29 14:38   ` Bruce Richardson
2015-09-29 14:48     ` Chilikin, Andrey
2015-09-29 14:53       ` Bruce Richardson
2015-09-29 14:26 ` [dpdk-dev] [PATCH 2/3] i40e: add RTE_ETH_FDIR_OTHER processing " Andrey Chilikin
2015-09-29 14:26 ` [dpdk-dev] [PATCH 3/3] ixgbe: add check for supported flow director behaviors Andrey Chilikin
2015-09-30 13:43 ` [dpdk-dev] [PATCH v2 0/3] Support for flow director behavior "passthru" on Intel FVL NIC Andrey Chilikin
2015-09-30 13:43   ` [dpdk-dev] [PATCH v2 1/3] librte_ether: add RTE_ETH_FDIR_PASSTHRU for flow director behavior Andrey Chilikin
2015-09-30 13:43   ` [dpdk-dev] [PATCH v2 2/3] i40e: add RTE_ETH_FDIR_PASSTHRU processing " Andrey Chilikin
2015-09-30 13:43   ` [dpdk-dev] [PATCH v2 3/3] ixgbe: add check for supported flow director behaviors Andrey Chilikin
2015-10-19  1:51   ` Wu, Jingjing [this message]
2015-11-04 21:54     ` [dpdk-dev] [PATCH v2 0/3] Support for flow director behavior "passthru" on Intel FVL NIC Thomas Monjalon

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=9BB6961774997848B5B42BEC655768F8D031E2@SHSMSX104.ccr.corp.intel.com \
    --to=jingjing.wu@intel.com \
    --cc=andrey.chilikin@intel.com \
    --cc=dev@dpdk.org \
    /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).