From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id ECBBEA046B for ; Thu, 27 Jun 2019 12:52:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id C9F5D20BD; Thu, 27 Jun 2019 12:52:18 +0200 (CEST) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id C0ED41E2F for ; Thu, 27 Jun 2019 12:52:16 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jun 2019 03:52:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.63,423,1557212400"; d="scan'208";a="189018655" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by fmsmga002.fm.intel.com with ESMTP; 27 Jun 2019 03:52:14 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.140]) by IRSMSX108.ger.corp.intel.com ([169.254.11.46]) with mapi id 14.03.0439.000; Thu, 27 Jun 2019 11:52:14 +0100 From: "Singh, Jasvinder" To: Thomas Monjalon CC: "dev@dpdk.org" , "Dumitrescu, Cristian" Thread-Topic: [dpdk-dev] [PATCH v2 00/28] sched: feature enhancements Thread-Index: AQHVK2tE1G0g5OqtUkGtdrCmQ/bqgKauZheAgADvpjA= Date: Thu, 27 Jun 2019 10:52:13 +0000 Message-ID: <54CBAA185211B4429112C315DA58FF6D3FD63C66@IRSMSX103.ger.corp.intel.com> References: <20190528120553.2992-2-lukaszx.krakowiak@intel.com> <20190625153217.24301-1-jasvinder.singh@intel.com> <5022647.LnWanB60ff@xps> In-Reply-To: <5022647.LnWanB60ff@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTIzMzUxMzgtM2YzOC00ZjAyLThkYzUtODZiMTFkODE4ZjgxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoicG9CNExuSXc1S21pZkRGd0xFcENoNHhWbjlIbXZGR0tSZHBLTkhRbk9CMzM5RDdqS3Q2VkU4YkYwY1wvMG9nVHoifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 00/28] sched: feature enhancements 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" > -----Original Message----- > From: Thomas Monjalon [mailto:thomas@monjalon.net] > Sent: Wednesday, June 26, 2019 10:34 PM > To: Singh, Jasvinder > Cc: dev@dpdk.org; Dumitrescu, Cristian > Subject: Re: [dpdk-dev] [PATCH v2 00/28] sched: feature enhancements >=20 > 25/06/2019 17:31, Jasvinder Singh: > > Jasvinder Singh (27): > > sched: update macros for flexible config > > sched: update subport and pipe data structures > > sched: update internal data structures > > sched: update port config API > > sched: update port free API > > sched: update subport config API > > sched: update pipe profile add API > > sched: update pipe config API > > sched: update pkt read and write API > > sched: update subport and tc queue stats > > sched: update port memory footprint API > > sched: update packet enqueue API > > sched: update grinder pipe and tc cache > > sched: update grinder next pipe and tc functions > > sched: update pipe and tc queues prefetch > > sched: update grinder wrr compute function > > sched: modify credits update function > > sched: update mbuf prefetch function > > sched: update grinder schedule function > > sched: update grinder handle function > > sched: update packet dequeue API > > sched: update sched queue stats API > > test/sched: update unit test > > net/softnic: update softnic tm function > > examples/qos_sched: update qos sched sample app > > examples/ip_pipeline: update ip pipeline sample app > > sched: code cleanup >=20 > I feel the titles of type "update some API" might be more meaningful if g= iving > the intent (flexibility) or more context (what is updated). > Not sure because I don't know this library enough. We will figure out better names in next version :) Thanks, Jasvinder