From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 389EA2BB0 for ; Wed, 19 Apr 2017 03:23:56 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Apr 2017 18:23:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,219,1488873600"; d="scan'208";a="91482697" Received: from fmsmsx107.amr.corp.intel.com ([10.18.124.205]) by fmsmga006.fm.intel.com with ESMTP; 18 Apr 2017 18:23:55 -0700 Received: from shsmsx152.ccr.corp.intel.com (10.239.6.52) by fmsmsx107.amr.corp.intel.com (10.18.124.205) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 18 Apr 2017 18:23:55 -0700 Received: from shsmsx102.ccr.corp.intel.com ([169.254.2.246]) by SHSMSX152.ccr.corp.intel.com ([169.254.6.217]) with mapi id 14.03.0319.002; Wed, 19 Apr 2017 09:23:53 +0800 From: "Lu, Wenzhuo" To: Adrien Mazarguil , "O'Driscoll, Tim" CC: "dev@dpdk.org" Thread-Topic: [dpdk-dev] 17.08 Roadmap Thread-Index: AdK1If/It67vs792SIiOLy+pkJXlPf//jRgA//h9JFA= Date: Wed, 19 Apr 2017 01:23:52 +0000 Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC09093B59A732@shsmsx102.ccr.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA75A65453@IRSMSX108.ger.corp.intel.com> <20170414143002.GN3790@6wind.com> In-Reply-To: <20170414143002.GN3790@6wind.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] 17.08 Roadmap X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Apr 2017 01:23:57 -0000 Hi Adrien, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Adrien Mazarguil > Sent: Friday, April 14, 2017 10:30 PM > To: O'Driscoll, Tim > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] 17.08 Roadmap >=20 > On Fri, Apr 14, 2017 at 01:27:13PM +0000, O'Driscoll, Tim wrote: > > > > API to Configure Queue Regions for RSS: This provides support for > configuration of queue regions for RSS, so that different traffic classes= or > different packet classification types to be separated into different queu= es. > This will be implemented for I40E. >=20 > About this last topic, do you mean devising a new API is necessary or do = you > plan to implement it through rte_flow? I'm asking as it looks like this i= s what > the rte_flow RSS action is defined for, see [1]. The mlx5 PMD adds suppor= t > for it in 17.05 [2]. Yes. We'll try to use rte_flow if appropriate. And this RSS action is plann= ed to be used. >=20 > I also intend to submit a few changes to rte_flow: >=20 > - VLAN item fix (according to this thread [3]). Impacts PMDs that impleme= nt > the VLAN and associated items. Not sure it can be accepted or 17.08 due= to > ABI breakage, but it will be submitted regardless. BTW, Ixgbe has removed the tpid check. http://dpdk.org/dev/patchwork/patch/23637= / I don't find another one using tpid. So, PMD should be ready. We can remove the tpid from rte now. >=20 > - A new isolated operation mode for rte_flow, guaranteeing applications c= an > expect to receive packets from the flow rules they define *only* for > complete control. No more "default" RX rules, RSS and so on. It means > PMDs > are free to reassign these resources to flow rules. No planned ABI > breakage. >=20 > [1] http://dpdk.org/doc/guides/prog_guide/rte_flow.html#action-rss > [2] http://dpdk.org/browse/next/dpdk-next- > net/commit/?id=3D1bfb7bb4423349ab13decead0af8ffd006e8e398 > [3] http://dpdk.org/ml/archives/dev/2017-March/060231.html >=20 > -- > Adrien Mazarguil > 6WIND