Message ID | 1443536800-13269-2-git-send-email-andrey.chilikin@intel.com (mailing list archive) |
---|---|
State | Superseded, archived |
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id 0F2327E23; Tue, 29 Sep 2015 16:27:32 +0200 (CEST) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 64495B62 for <dev@dpdk.org>; Tue, 29 Sep 2015 16:27:27 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP; 29 Sep 2015 07:27:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.17,608,1437462000"; d="scan'208";a="779932711" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by orsmga001.jf.intel.com with ESMTP; 29 Sep 2015 07:27:05 -0700 Received: from sivswdev02.ir.intel.com (sivswdev02.ir.intel.com [10.237.217.46]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id t8TER4lw032483; Tue, 29 Sep 2015 15:27:04 +0100 Received: from sivswdev02.ir.intel.com (localhost [127.0.0.1]) by sivswdev02.ir.intel.com with ESMTP id t8TER4cZ013525; Tue, 29 Sep 2015 15:27:04 +0100 Received: (from achiliki@localhost) by sivswdev02.ir.intel.com with id t8TER4Nh013519; Tue, 29 Sep 2015 15:27:04 +0100 From: Andrey Chilikin <andrey.chilikin@intel.com> To: dev@dpdk.org Date: Tue, 29 Sep 2015 15:26:38 +0100 Message-Id: <1443536800-13269-2-git-send-email-andrey.chilikin@intel.com> X-Mailer: git-send-email 1.7.4.1 In-Reply-To: <1443536800-13269-1-git-send-email-andrey.chilikin@intel.com> References: <1443536800-13269-1-git-send-email-andrey.chilikin@intel.com> Subject: [dpdk-dev] [PATCH 1/3] librte_ether: add RTE_ETH_FDIR_OTHER for flow director behavior X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Commit Message
Chilikin, Andrey
Sept. 29, 2015, 2:26 p.m. UTC
Add new flow director behavior RTE_ETH_FDIR_OTHER to assign a queue by other filters
Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com>
---
lib/librte_ether/rte_eth_ctrl.h | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
Comments
On Tue, Sep 29, 2015 at 03:26:38PM +0100, Andrey Chilikin wrote: > Add new flow director behavior RTE_ETH_FDIR_OTHER to assign a queue by other filters > > Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com> > --- > lib/librte_ether/rte_eth_ctrl.h | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > diff --git a/lib/librte_ether/rte_eth_ctrl.h b/lib/librte_ether/rte_eth_ctrl.h > index 26b7b33..3acf501 100644 > --- a/lib/librte_ether/rte_eth_ctrl.h > +++ b/lib/librte_ether/rte_eth_ctrl.h > @@ -417,6 +417,7 @@ struct rte_eth_fdir_input { > enum rte_eth_fdir_behavior { > RTE_ETH_FDIR_ACCEPT = 0, > RTE_ETH_FDIR_REJECT, > + RTE_ETH_FDIR_OTHER, > }; > > /** > -- > 1.7.4.1 > Is "OTHER" meant to be a "NOOP" or a generic hold-all for a set of other possible behaviours. From the description, I would assume NOOP - in which case would RTE_ETH_FDIR_NOOP not be a better name? /Bruce
> -----Original Message----- > From: Richardson, Bruce > Sent: Tuesday, September 29, 2015 3:38 PM > To: Chilikin, Andrey > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] [PATCH 1/3] librte_ether: add RTE_ETH_FDIR_OTHER > for flow director behavior > > On Tue, Sep 29, 2015 at 03:26:38PM +0100, Andrey Chilikin wrote: > > Add new flow director behavior RTE_ETH_FDIR_OTHER to assign a queue by > > other filters > > > > Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com> > > --- > > lib/librte_ether/rte_eth_ctrl.h | 1 + > > 1 files changed, 1 insertions(+), 0 deletions(-) > > > > diff --git a/lib/librte_ether/rte_eth_ctrl.h > > b/lib/librte_ether/rte_eth_ctrl.h index 26b7b33..3acf501 100644 > > --- a/lib/librte_ether/rte_eth_ctrl.h > > +++ b/lib/librte_ether/rte_eth_ctrl.h > > @@ -417,6 +417,7 @@ struct rte_eth_fdir_input { enum > > rte_eth_fdir_behavior { > > RTE_ETH_FDIR_ACCEPT = 0, > > RTE_ETH_FDIR_REJECT, > > + RTE_ETH_FDIR_OTHER, > > }; > > > > /** > > -- > > 1.7.4.1 > > > Is "OTHER" meant to be a "NOOP" or a generic hold-all for a set of other > possible behaviours. From the description, I would assume NOOP - in which > case would RTE_ETH_FDIR_NOOP not be a better name? > > /Bruce "NOOP" sounds like no operation at all, but FD still performs matching and extracts flexible payload to the RX descriptor, it only skips queue assignment which is done by other filters with lower priority. Maybe RTE_ETH_FDIR_PASSTHRU? Regards, Andrey
On Tue, Sep 29, 2015 at 03:48:32PM +0100, Chilikin, Andrey wrote: > > -----Original Message----- > > From: Richardson, Bruce > > Sent: Tuesday, September 29, 2015 3:38 PM > > To: Chilikin, Andrey > > Cc: dev@dpdk.org > > Subject: Re: [dpdk-dev] [PATCH 1/3] librte_ether: add RTE_ETH_FDIR_OTHER > > for flow director behavior > > > > On Tue, Sep 29, 2015 at 03:26:38PM +0100, Andrey Chilikin wrote: > > > Add new flow director behavior RTE_ETH_FDIR_OTHER to assign a queue by > > > other filters > > > > > > Signed-off-by: Andrey Chilikin <andrey.chilikin@intel.com> > > > --- > > > lib/librte_ether/rte_eth_ctrl.h | 1 + > > > 1 files changed, 1 insertions(+), 0 deletions(-) > > > > > > diff --git a/lib/librte_ether/rte_eth_ctrl.h > > > b/lib/librte_ether/rte_eth_ctrl.h index 26b7b33..3acf501 100644 > > > --- a/lib/librte_ether/rte_eth_ctrl.h > > > +++ b/lib/librte_ether/rte_eth_ctrl.h > > > @@ -417,6 +417,7 @@ struct rte_eth_fdir_input { enum > > > rte_eth_fdir_behavior { > > > RTE_ETH_FDIR_ACCEPT = 0, > > > RTE_ETH_FDIR_REJECT, > > > + RTE_ETH_FDIR_OTHER, > > > }; > > > > > > /** > > > -- > > > 1.7.4.1 > > > > > Is "OTHER" meant to be a "NOOP" or a generic hold-all for a set of other > > possible behaviours. From the description, I would assume NOOP - in which > > case would RTE_ETH_FDIR_NOOP not be a better name? > > > > /Bruce > "NOOP" sounds like no operation at all, but FD still performs matching and > extracts flexible payload to the RX descriptor, it only skips queue assignment > which is done by other filters with lower priority. Maybe RTE_ETH_FDIR_PASSTHRU? > > Regards, > Andrey PASSTHRU seems good to me. It's clearer than "OTHER" anyway :-) /Bruce
diff --git a/lib/librte_ether/rte_eth_ctrl.h b/lib/librte_ether/rte_eth_ctrl.h index 26b7b33..3acf501 100644 --- a/lib/librte_ether/rte_eth_ctrl.h +++ b/lib/librte_ether/rte_eth_ctrl.h @@ -417,6 +417,7 @@ struct rte_eth_fdir_input { enum rte_eth_fdir_behavior { RTE_ETH_FDIR_ACCEPT = 0, RTE_ETH_FDIR_REJECT, + RTE_ETH_FDIR_OTHER, }; /**