From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id E77832BF5 for ; Thu, 26 Jan 2017 21:39:59 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga104.jf.intel.com with ESMTP; 26 Jan 2017 12:39:58 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,291,1477983600"; d="scan'208";a="1118304880" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga002.fm.intel.com with ESMTP; 26 Jan 2017 12:39:58 -0800 Received: from fmsmsx126.amr.corp.intel.com (10.18.125.43) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 26 Jan 2017 12:39:58 -0800 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.130]) by FMSMSX126.amr.corp.intel.com ([169.254.1.200]) with mapi id 14.03.0248.002; Thu, 26 Jan 2017 12:39:58 -0800 From: "Eads, Gage" To: Jerin Jacob CC: "Richardson, Bruce" , "'dev@dpdk.org'" , "'thomas.monjalon@6wind.com'" , "'hemant.agrawal@nxp.com'" , "Van Haaren, Harry" , "McDaniel, Timothy" Thread-Topic: [dpdk-dev] [PATCH v4 1/6] eventdev: introduce event driven programming model Thread-Index: AQHSd7gUsGgHA6bcOUyrfHLc4sbJyaFLK1Fg Date: Thu, 26 Jan 2017 20:39:57 +0000 Message-ID: <9184057F7FC11744A2107296B6B8EB1E01E5F76C@FMSMSX108.amr.corp.intel.com> References: <1480996340-29871-1-git-send-email-jerin.jacob@caviumnetworks.com> <1482312326-2589-1-git-send-email-jerin.jacob@caviumnetworks.com> <1482312326-2589-2-git-send-email-jerin.jacob@caviumnetworks.com> <9184057F7FC11744A2107296B6B8EB1E01E5EF2C@FMSMSX108.amr.corp.intel.com> <59AF69C657FD0841A61C55336867B5B035B8EBB9@IRSMSX103.ger.corp.intel.com> <9184057F7FC11744A2107296B6B8EB1E01E5F0AC@FMSMSX108.amr.corp.intel.com> <9184057F7FC11744A2107296B6B8EB1E01E5F3D3@FMSMSX108.amr.corp.intel.com> <20170126093924.GA5276@localhost.localdomain> In-Reply-To: <20170126093924.GA5276@localhost.localdomain> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTdkYjZjODUtMGJlZC00ZDcxLWI3YWItNzZiZTgyZmJmZWI0IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS45LjYuNiIsIlRydXN0ZWRMYWJlbEhhc2giOiJjbjBXUGxUQnVYM1JHTUduR0M4MGZxbDVGUEw0YXhQdHUyZzh5TDBiXC91dz0ifQ== x-ctpclassification: CTP_PUBLIC x-originating-ip: [10.1.200.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v4 1/6] eventdev: introduce event driven programming model 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: Thu, 26 Jan 2017 20:40:00 -0000 > -----Original Message----- > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com] > Sent: Thursday, January 26, 2017 3:39 AM > To: Eads, Gage > Cc: Richardson, Bruce ; 'dev@dpdk.org' > ; 'thomas.monjalon@6wind.com' > ; 'hemant.agrawal@nxp.com' > ; Van Haaren, Harry > ; McDaniel, Timothy > > Subject: Re: [dpdk-dev] [PATCH v4 1/6] eventdev: introduce event driven > programming model > =20 > On Wed, Jan 25, 2017 at 10:36:21PM +0000, Eads, Gage wrote: > > > > > > Subject: [dpdk-dev] [PATCH > > > v4 > 1/6] eventdev: introduce event driven > > programming model > > > > > > > > +/** > > + * Enqueue > > > a burst > of events objects or an event object supplied > > in > > > > > > *rte_event* > > + * structure on an event device designated > > > by its > *dev_id* > > through the event + * port specified by > > > *port_id*. Each > event > > object specifies the event queue on + > > > * which it will be > enqueued. > > > > > > + * > > > > > > + * The *nb_events* parameter is the number of event > > > objects to > > > enqueue which are + * supplied in the *ev* array > > > of *rte_event* > > > structure. > > > > > > + * > > > > > > + * The rte_event_enqueue_burst() function returns the > > > number of > + > > * events objects it actually enqueued. A return > > > value equal to > > > *nb_events* + * means that all event objects = have > been enqueued. > > > > > > + * > > > > > > + * @param dev_id > > > > > > + * The identifier of the device. > > > > > > + * @param port_id > > > > > > + * The identifier of the event port. > > > > > > + * @param ev > > > > > > + * Points to an array of *nb_events* objects of type *rt= e_event* > > > > > structure > > > > > > + * which contain the event object enqueue operations to = be > > > > > processed. > > > > > > + * @param nb_events > > > > > > + * The number of event objects to enqueue, typically num= ber of > > > > > > + * rte_event_port_enqueue_depth() available for this por= t. > > > > > > + * > > > > > > + * @return > > > > > > + * The number of event objects actually enqueued on the = event > > > > > device. The > > > > > > + * return value can be less than the value of the *nb_ev= ents* > > > > > parameter > > > > > > when > > > > > > + * the event devices queue is full or if invalid paramet= ers are > > > > > specified in a > > > > > > + * *rte_event*. If return value is less than *nb_events*= , the > > > > > remaining events > > > > > > + * at the end of ev[] are not consumed,and the caller ha= s to take > > > > > care of > > > > > > them > > > > > > + * > > > > > > + * @see rte_event_port_enqueue_depth() + */ +uint16_t > > > > > > +rte_event_enqueue_burst(uint8_t dev_id, uint8_t port_id, > > > > > > + const struct rte_event ev[], uint16_t > nb_events); > > > > > > > > > > There are a number of reasons this operation could fail to > > > enqueue > all > the events, including: > > > > > - Backpressure > > > > > - Invalid port ID > > > > > - Invalid queue ID > > > > > - Invalid sched type when a queue is configured for > > > ATOMIC_ONLY, > > ORDERED_ONLY, or PARALLEL_ONLY > - ... > > > > > > > > > > The current API doesn't provide a straightforward way to > > > determine > the > cause of a failure. This is a particular issue > > > on event PMDs > that can > backpressure, where the app may want to > > > treat that case > differently > than the other failure cases. > > > > > > > > > > Could we change the return type to int16_t, and define a set > > > of > error > cases (e.g. -ENOSPC for backpressure, -EINVAL for an > > > invalid argument)? > > > > > (With corresponding changes needed in the PMD API) Similarly > > > we > could > change rte_event_dequeue_burst() to return an > > > int16_t, with > -EINVAL as > a possible error case. > > > > > > > > Use rte_errno instead, I suggest. That's what it's there for. > > > > > > > > /Bruce > > > > > > That makes sense. In that case, the API comment could be tweaked li= ke so: > > > > > > * If the return value is less than *nb_events*, the remaining eve= nts at the > > > * end of ev[] are not consumed and the caller has to take care of= them, > and > > > * rte_errno is set accordingly. Possible errno values include: > > > * - EINVAL - The port ID is invalid, an event's queue ID is inval= id, or an > > > * event's sched type doesn't match the capabilities of= the > > > * destination queue. > > > * - ENOSPC - The event port was backpressured and unable to enque= ue > one or > > > * more events. > > > > However it seems better to use a signed integer for the dequeue burst = return > value, if it is to use rte_errno. Application code could be simplified: > > > > (signed return value) > > ret =3D rte_event_dequeue_burst(...); > > if (ret < 0) > > rte_panic("Dequeued returned errno %d\n", rte_errno); > > > > vs. > > > > (unsigned return value) > > ret =3D rte_event_dequeue_burst(...); > > if (ret =3D=3D 0 && rte_errno !=3D 0) > > rte_panic("Dequeued returned errno %d\n", rte_errno); > > > > And with an unsigned return value, all dequeue implementations would h= ave > to clear rte_errno when no events are dequeued. After some internal discussion, I don't think the signed return value is ne= cessary for burst dequeue. Burst enqueue is the more interesting case... > =20 > Gage, > =20 > Just to understand, what is the expected application behavior if the > implementation returns -ENOSPC It's application-dependent -- depending on the importance of the event, the= application could decide to retry the enqueue some number of times or deci= de to drop the event. > =20 > Apart for the above SW driver behavior, I think, HW implementation has t= wo > more different behavior > a) Implementation make sure that it never returns -ENOSPC by allocating = more > space on the fly or any other scheme > b) Tail drop > =20 By "tail drop," do you mean the hardware drops the event (and presumably fr= ees any memory it points to)? Or the enqueue is unsuccessful and the applic= ation drops the event? > Considering different implementation has different behaviors, How about > enumerating the overflow policy at the port configuration time? and let > implementation act accordingly to avoid fast-patch change in > application(effects in all implementation irrespective of the capability= ) > =20 > possible enumerating value at the port configuration time, > - PANIC or similar scheme to denote it cannot proceed > - TAIL DROP > or any expected application behavior you want to add I wonder if that's necessary? Hardware behavior a) means the function will = always return nb_events. If hardware drops the event(s), I assume enqueue_b= urst would still return nb_events and the app behaves as if all events were= sent. If the enqueue fails (ret < nb_events), app software could check rte= _errno and take the action it deems necessary. So all fast-path enqueue cod= e could look like: ret =3D rte_event_enqueue_burst(..., nb_events); if (ret < nb_events) { .... }