From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 729002C4F for ; Mon, 7 Aug 2017 10:33:47 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Aug 2017 01:33:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,336,1498546800"; d="scan'208";a="1202823970" Received: from kmsmsx154.gar.corp.intel.com ([172.21.73.14]) by fmsmga002.fm.intel.com with ESMTP; 07 Aug 2017 01:33:44 -0700 Received: from pgsmsx103.gar.corp.intel.com ([169.254.2.44]) by KMSMSX154.gar.corp.intel.com ([169.254.12.48]) with mapi id 14.03.0319.002; Mon, 7 Aug 2017 16:33:44 +0800 From: "Zhao1, Wei" To: Adrien Mazarguil , "Lu, Wenzhuo" CC: TETSURO NAKAMURA , "Mcnamara, John" , TAKADA Naoki , "Satoshi NISHIYAMA" , "dev@dpdk.org" Thread-Topic: using rte_flow via tespmd with Intel X552 Thread-Index: AQHTCrkvXV891Tfop0WN4dHK2iu9B6Jv8kWAgAC14bD//9sCgIAAC0YAgAgGtSA= Date: Mon, 7 Aug 2017 08:33:43 +0000 Message-ID: References: <725d0083-decc-1427-c0c1-b8c3515aa429@lab.ntt.co.jp> <42be0cc3-a69b-4e07-be84-41a8deba75cf@lab.ntt.co.jp> <6A0DE07E22DDAD4C9103DF62FEBC09093B67FA3F@shsmsx102.ccr.corp.intel.com> <20170802134108.GX19852@6wind.com> In-Reply-To: <20170802134108.GX19852@6wind.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [172.30.20.206] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] using rte_flow via tespmd with Intel X552 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: Mon, 07 Aug 2017 08:33:48 -0000 Hi, Adrien > -----Original Message----- > From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com] > Sent: Wednesday, August 2, 2017 9:41 PM > To: Lu, Wenzhuo > Cc: Zhao1, Wei ; TETSURO NAKAMURA > ; Mcnamara, John > ; TAKADA Naoki ; > Satoshi NISHIYAMA ; dev@dpdk.org > Subject: Re: using rte_flow via tespmd with Intel X552 >=20 > Hi Wenzhuo, >=20 > On Wed, Aug 02, 2017 at 01:00:47PM +0000, Lu, Wenzhuo wrote: > > Hi, > > > > > -----Original Message----- > > > From: Zhao1, Wei > > > Sent: Wednesday, August 2, 2017 3:28 AM > > > To: TETSURO NAKAMURA > > > Cc: TAKADA Naoki ; Satoshi NISHIYAMA > > > ; Lu, Wenzhuo ; > > > dev@dpdk.org > > > Subject: RE: using rte_flow via tespmd with Intel X552 > > > > > > Hi, NAKAMURA > > > > > > I have upload 2 documents about command format when creating flow > > > for NIC igb and ixgbe in the email attachment. > > > I have decided to commit the context in the doc to > > > doc\guides\nics\ixgbe.rst before, BUT by now it seems the content of > > > the document is too much To store there. So, is there any other doc m= ore > suitable in DPDK to record this. > > > And welcome for any other suggestion. > > > AND, Wenzhuo, what is your opinion for this? > > I also have the same feeling that it may make the ixgbe.rst too big. > > + John and Adrien. Hi John, Adrien, I'm think about creating a specifi= c doc > for rte flow, we can include the examples for every NIC here. Is it good?= If so, > where's the good place to put it? Thanks. >=20 > Depends on the kind of examples. Code samples or testpmd flow command? > Unless you mean a document that describes individual rte_flow features > supported by each NIC? >=20 > Code samples could be added to a new "Programming flow rules" (or > something) section in doc/guide/prog_guide/rte_flow.rst. >=20 > Another section about NICs could be added in that documentation as well > but should only contain a short summary for each of them and a link to th= e > relevant PMD documentation in nics/$PMD.rst (or elsewhere in the DPDK > tree), if any. >=20 > If you want to describe individual rte_flow features supported by each NI= C, I > think there's no other choice but to create a bunch of > doc/guides/nics/features/rte_flow/*.ini files. Your suggestion of create a bunch under > doc/guides/nics/features/rte_flow= /*.ini to record these for every type of NIC of igb/ixgbe/i40e, It seems very reasonable, but will DPDK community will agree to such a big = change for this a specific feature? Maybe your suggestion of "in doc/guide/prog_guide/rte_flow.rst, add a sh= ort summary for each of them and a link to the relevant PMD documentation in nics/$PMD.rst ". and also record to doc\guides\nics\ixgbe.rst will be the only feasible sche= me? Although it will be too much to store. Wenzhuo and Adrien, If none of you has no objection to this, I will impleme= nt as Adrien's first suggestion. Thank you. >=20 > > > > -----Original Message----- > > > > From: TETSURO NAKAMURA [mailto:nakamura.tetsuro@lab.ntt.co.jp] > > > > Sent: Wednesday, August 2, 2017 12:22 PM > > > > To: Zhao1, Wei > > > > Cc: TAKADA Naoki ; Satoshi NISHIYAMA > > > > ; Lu, Wenzhuo ; > > > > dev@dpdk.org > > > > Subject: Re: using rte_flow via tespmd with Intel X552 > > > > > > > > Wei Zhao - san > > > > (Cc'ing Wenzhuo - san) > > > > > > > > According to the e-mail thread [1] in April, you have a document > > > > about command format when creating flows on ixgbe NIC. > > > > > > > > I would appreciate your uploading that document to community or > > > > could you just share it with me via an e-mail ?? > > > > > > > > [1] http://dpdk.org/ml/archives/users/2017-April/001786.html > > > > > > > > Thanks, > > > > > > > > Tetsuro > > > > > > > > # re-sending the e-mail because I failed to submit the e-mail to > > > > users@dpdk.org. > > > > > > > > -- > > > > Tetsuro Nakamura NTT Network > > > > Service Systems Laboratories > > > > TEL:0422 59 6914(National)/+81 422 59 6914(International) 3-9-11, > > > > Midori-Cho Musashino-Shi, Tokyo 180-8585 Japan > > > > > > >=20 > -- > Adrien Mazarguil > 6WIND