From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 9F7325598 for ; Fri, 28 Oct 2016 15:49:01 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP; 28 Oct 2016 06:49:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,410,1473145200"; d="scan'208";a="24849204" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by orsmga005.jf.intel.com with ESMTP; 28 Oct 2016 06:48:59 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.226]) by IRSMSX103.ger.corp.intel.com ([169.254.3.190]) with mapi id 14.03.0248.002; Fri, 28 Oct 2016 14:48:57 +0100 From: "Van Haaren, Harry" To: Jerin Jacob Thread-Topic: [dpdk-dev] [RFC] [PATCH v2] libeventdev: event driven programming model framework for DPDK Thread-Index: AQHSLug4Mxw97Qgi5U2Ssk9lNdMcHaC947JA Date: Fri, 28 Oct 2016 13:48:57 +0000 Message-ID: References: <20161005072451.GA2358@localhost.localdomain> <1476214216-31982-1-git-send-email-jerin.jacob@caviumnetworks.com> <20161025174904.GA18333@localhost.localdomain> In-Reply-To: <20161025174904.GA18333@localhost.localdomain> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYTk1NGFjMTMtODgxYy00NzllLWE0MGItOTljOTUyZTFhNjcwIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InE3SzF3Mjd5THJacVYzZXdWdGdabmVHanBVQTEyMUI2V1NSaG8xaWFsUEU9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "Vangati, Narender" , "dev@dpdk.org" , "Eads, Gage" , "thomas.monjalon@6wind.com" Subject: Re: [dpdk-dev] [RFC] [PATCH v2] libeventdev: event driven programming model framework for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Oct 2016 13:49:02 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jerin Jacob > Sent: Tuesday, October 25, 2016 6:49 PM >=20 > Hi Community, >=20 > So far, I have received constructive feedback from Intel, NXP and Linaro = folks. > Let me know, if anyone else interested in contributing to the definition = of eventdev? >=20 > If there are no major issues in proposed spec, then Cavium would like wor= k on > implementing and up-streaming the common code(lib/librte_eventdev/) and > an associated HW driver.(Requested minor changes of v2 will be addressed > in next version). Hi All, I've been looking at the eventdev API from a use-case point of view, and I'= m unclear on a how the API caters for two uses. I have simplified these as = much as possible, think of them as a theoretical unit-test for the API :) Fragmentation: 1. Dequeue 8 packets 2. Process 2 packets 3. Processing 3rd, this packet needs fragmentation into two packets 4. Process remaining 5 packets as normal What function calls does the application make to achieve this? In particular, I'm referring to how can the scheduler know that the 3rd pac= ket is the one being fragmented, and how to keep packet order valid.=20 Dropping packets: 1. Dequeue 8 packets 2. Process 2 packets 3. Processing 3rd, this packet needs to be dropped 4. Process remaining 5 packets as normal What function calls does the application make to achieve this? Again, in particular how does the scheduler know that the 3rd packet is bei= ng dropped. Regards, -Harry