From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 147BABB0E for ; Wed, 26 Oct 2016 14:11:21 +0200 (CEST) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga103.jf.intel.com with ESMTP; 26 Oct 2016 05:11:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,550,1473145200"; d="scan'208";a="1050427929" Received: from irsmsx104.ger.corp.intel.com ([163.33.3.159]) by orsmga001.jf.intel.com with ESMTP; 26 Oct 2016 05:11:06 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.226]) by IRSMSX104.ger.corp.intel.com ([163.33.3.159]) with mapi id 14.03.0248.002; Wed, 26 Oct 2016 13:11:04 +0100 From: "Van Haaren, Harry" To: Jerin Jacob , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC] [PATCH v2] libeventdev: event driven programming model framework for DPDK Thread-Index: AQHSLug4Mxw97Qgi5U2Ssk9lNdMcHaC6lrPg Date: Wed, 26 Oct 2016 12:11:03 +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: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZDBjNjRkODEtMTkyMS00Mjg4LTlmNTgtN2QyOThmYzA1MGFmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjNBTXVURkp0M3M3eEtKWnVKUXVhMm9vbGIyVjdTckRGWXllZllSVDlWQ009In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "Vangati, Narender" , "thomas.monjalon@6wind.com" , "Eads, Gage" 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: Wed, 26 Oct 2016 12:11:22 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jerin Jacob >=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 will propose a minor change to the rte_event struct, allowing some bits t= o be implementation specific. Currently the rte_event struct has no space t= o allow an implementation store any metadata about the event. For software = performance it would be really helpful if there are some bits available for= the implementation to keep some flags about each event. I suggest to rework the struct as below which opens 6 bits that were otherw= ise wasted, and define them as implementation specific. By implementation s= pecific it is understood that the implementation can overwrite any informat= ion stored in those bits, and the application must not expect the data to r= emain after the event is scheduled. OLD: struct rte_event { uint32_t flow_id:24; uint32_t queue_id:8; uint8_t sched_type; /* Note only 2 bits of 8 are required */ NEW: struct rte_event { uint32_t flow_id:24; uint32_t sched_type:2; /* reduced size : but 2 bits is enough for the enqu= eue types Ordered,Atomic,Parallel.*/ uint32_t implementation:6; /* available for implementation specific metada= ta */ uint8_t queue_id; /* still 8 bits as before */ Thoughts? -Harry