DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Stillwell Jr, Paul M" <paul.m.stillwell.jr@intel.com>,
	"wei.zhao1@intel.com" <"Wei Zhao"@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Ye, Xiaolong" <xiaolong.ye@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/7] add switch filter support for intel DCF
Date: Sun, 15 Mar 2020 02:19:02 +0000	[thread overview]
Message-ID: <039ED4275CED7440929022BC67E70611547E0B3A@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <MW3PR11MB45386F43B66D5FB662730017E0FA0@MW3PR11MB4538.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Stillwell Jr, Paul M <paul.m.stillwell.jr@intel.com>
> Sent: Saturday, March 14, 2020 12:13 AM
> To: wei.zhao1@intel.com <"Wei Zhao"@dpdk.org>; dev@dpdk.org
> Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Ye, Xiaolong <xiaolong.ye@intel.com>
> Subject: RE: [dpdk-dev] [PATCH 0/7] add switch filter support for intel DCF
> 
> This patch set is confusing to me. Only the DCF can deal with switch rules so
> why is the ice PMD trying to do anything with switch rules related to DCF?

Ice pf PMD already implemented the switch rule engine and some parsers for PF only usage
The ice DCF just share same engine and add some new parsers for DCF usage.
And as I explained in another email, it is the case that the same compiled code can support different usage at runtime.

Thanks
Qi

> 
> Paul
> 
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of wei.zhao1@intel.com
> > Sent: Thursday, March 12, 2020 6:04 PM
> > To: dev@dpdk.org
> > Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Ye, Xiaolong
> > <xiaolong.ye@intel.com>
> > Subject: [dpdk-dev] [PATCH 0/7] add switch filter support for intel
> > DCF
> >
> > A DCF (Device Config Function) framework has been add for intel
> > device, this patch set add add switch filter support for it, this set
> > also fix bugs which block this feature.
> >
> > This patchset is based on:
> > [1] https://patchwork.dpdk.org/cover/66480/ : add Intel DCF PMD
> > support
> >
> > Depends-on: series-8859
> >
> >
> > wei zhao (7):
> >   net/ice: enable switch flow on DCF
> >   net/ice: support for more PPPoE input set
> >   net/ice: change swicth parser to support flexible mask
> >   net/ice: add support for MAC VLAN rule
> >   net/ice: change default tunnle type
> >   net/ice: add action number check for swicth
> >   net/ice: fix input set of VLAN item
> >
> >  config/common_linux                 |   1 +
> >  drivers/net/ice/ice_dcf_ethdev.c    |  10 +-
> >  drivers/net/ice/ice_dcf_parent.c    |   7 +
> >  drivers/net/ice/ice_fdir_filter.c   |   6 +
> >  drivers/net/ice/ice_generic_flow.c  |  13 +
> >  drivers/net/ice/ice_generic_flow.h  |   9 +
> >  drivers/net/ice/ice_hash.c          |   6 +
> >  drivers/net/ice/ice_switch_filter.c | 461
> > ++++++++++++++++++----------
> >  8 files changed, 348 insertions(+), 165 deletions(-)
> >
> > --
> > 2.19.1
> 


  reply	other threads:[~2020-03-15  2:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13  1:04 wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 1/7] net/ice: enable switch flow on DCF wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 2/7] net/ice: support for more PPPoE input set wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 3/7] net/ice: change swicth parser to support flexible mask wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 4/7] net/ice: add support for MAC VLAN rule wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 5/7] net/ice: change default tunnle type wei.zhao1@intel.com
2020-03-13 16:14   ` Stillwell Jr, Paul M
2020-03-13  1:04 ` [dpdk-dev] [PATCH 6/7] net/ice: add action number check for swicth wei.zhao1@intel.com
2020-03-13  1:04 ` [dpdk-dev] [PATCH 7/7] net/ice: fix input set of VLAN item wei.zhao1@intel.com
2020-03-13 16:12 ` [dpdk-dev] [PATCH 0/7] add switch filter support for intel DCF Stillwell Jr, Paul M
2020-03-15  2:19   ` Zhang, Qi Z [this message]
2020-03-13  2:07 Wei Zhao

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=039ED4275CED7440929022BC67E70611547E0B3A@SHSMSX103.ccr.corp.intel.com \
    --to=qi.z.zhang@intel.com \
    --cc="Wei Zhao"@dpdk.org \
    --cc=dev@dpdk.org \
    --cc=paul.m.stillwell.jr@intel.com \
    --cc=xiaolong.ye@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).