DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Ergin, Mesut A" <mesut.a.ergin@intel.com>,
	"Xing, Beilei" <beilei.xing@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] net/i40e: add support for MARK + RSS action in rte_flow
Date: Wed, 22 May 2019 12:30:21 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153385EA5@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1557980885-183777-2-git-send-email-mesut.a.ergin@intel.com>



> -----Original Message-----
> From: Ergin, Mesut A
> Sent: Thursday, May 16, 2019 12:28 PM
> To: Xing, Beilei <beilei.xing@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: dev@dpdk.org; Ergin, Mesut A <mesut.a.ergin@intel.com>
> Subject: [PATCH 1/3] net/i40e: add support for MARK + RSS action in rte_flow
> 
> Currently, i40e Flow Director action parser only allows following nine action
> combinations: (QUEUE, PASSTHRU, DROP, QUEUE + MARK, PASSTHRU + MARK,
> DROP + MARK, QUEUE + FLAG, PASSTHRU + FLAG, DROP + FLAG)
> 
> Using the existing Cloud Filter profile on the NIC, it is possible to add support
> for two more combinations as: (MARK + RSS, MARK + FLAG +
> RSS)
> 
> Addition of these new combinations would allow more applications to utilize
> DPDK rte_flow to implement hardware flow offloads with Intel Ethernet 700
> series network adapters, including but not limited to the existing OVS DPDK
> partial hardware flow offload feature.
> 
> Signed-off-by: Mesut Ali Ergin <mesut.a.ergin@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi

  parent reply	other threads:[~2019-05-22 12:30 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-16  4:28 [dpdk-dev] [PATCH 0/3] net/i40e: improve rte_flow offload with MARK + RSS Mesut Ali Ergin
2019-05-16  4:28 ` Mesut Ali Ergin
2019-05-16  4:28 ` [dpdk-dev] [PATCH 1/3] net/i40e: add support for MARK + RSS action in rte_flow Mesut Ali Ergin
2019-05-16  4:28   ` Mesut Ali Ergin
2019-05-22 12:30   ` Zhang, Qi Z [this message]
2019-05-16  4:28 ` [dpdk-dev] [PATCH 2/3] net/i40e: add runtime option to disable vector rx Mesut Ali Ergin
2019-05-16  4:28   ` Mesut Ali Ergin
2019-05-16  8:17   ` Maxime Coquelin
2019-05-16  8:17     ` Maxime Coquelin
2019-05-16 21:26     ` Ergin, Mesut A
2019-05-20  8:29   ` Ananyev, Konstantin
2019-05-20 17:53     ` Ergin, Mesut A
2019-05-20 23:11       ` Ananyev, Konstantin
2019-05-21 16:33         ` Ergin, Mesut A
2019-05-21 17:20           ` Ananyev, Konstantin
2019-05-21 20:55             ` Ergin, Mesut A
2019-05-22 11:01               ` Ananyev, Konstantin
2019-05-22 14:05                 ` Thomas Monjalon
2019-05-22 14:32                   ` Zhang, Qi Z
2019-05-23 13:10                     ` Jerin Jacob Kollanukkaran
2019-05-23 17:54                 ` Ergin, Mesut A
2019-05-16  4:28 ` [dpdk-dev] [PATCH 3/3] net/i40e: fix inadvertent override of vector RX allowance Mesut Ali Ergin
2019-05-16  4:28   ` Mesut Ali Ergin
2019-05-16  8:17   ` Maxime Coquelin
2019-05-16  8:17     ` Maxime Coquelin
2019-05-16 20:57     ` Ergin, Mesut A
2019-05-22 12:42   ` Zhang, Qi Z
2019-05-23 18:25     ` Ergin, Mesut A
2019-05-24  2:39       ` Zhang, Qi Z
2019-05-24 18:08         ` Ergin, Mesut A
2019-05-25 11:29           ` Zhang, Qi Z

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=039ED4275CED7440929022BC67E7061153385EA5@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=mesut.a.ergin@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).