From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: eventdev: rte_event_dev_start() all queues are linked requirement Date: Mon, 30 Jul 2018 13:35:08 +0530 Message-ID: <20180730080507.GA15830@jerin> References: <21037D32-C2B9-40FF-92E6-55F6FA725E24@nokia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "dev@dpdk.org" , "Van Haaren, Harry" , mattias.ronnblom@ericsson.com To: "Elo, Matias (Nokia - FI/Espoo)" Return-path: Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0085.outbound.protection.outlook.com [104.47.42.85]) by dpdk.org (Postfix) with ESMTP id 0403E397D for ; Mon, 30 Jul 2018 10:15:46 +0200 (CEST) Content-Disposition: inline In-Reply-To: <21037D32-C2B9-40FF-92E6-55F6FA725E24@nokia.com> 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----- > Date: Mon, 30 Jul 2018 07:38:27 +0000 > From: "Elo, Matias (Nokia - FI/Espoo)" > To: "dev@dpdk.org" > CC: "jerin.jacob@caviumnetworks.com" , "Van > Haaren, Harry" > Subject: eventdev: rte_event_dev_start() all queues are linked requirement > x-mailer: Apple Mail (2.3445.9.1) > + mattias.ronnblom@ericsson.com as his SW driver is scheduled for next release. > > Hi, > > rte_event_dev_start() requires that all queues have to be linked, which makes > writing applications which link/unlink queues at runtime cumbersome. > E.g. the application has to dummy link all queues before rte_event_dev_start() > and then unlink them after the function call. This alone wouldn't be a big issue > but rte_event_dev_start() may also be called inside > rte_event_eth_rx_adapter_create() implementation causing additional complexity. > > To me this check seems more like eventdev implementation specific limitation, > which should be solved by the particular implementation and not enforced by the > API to all applications. From an application point of view enqueueing events to > an unlinked queue and expecting something meaningful to happen is an error > anyway. So, would it be conceivable to remove this particular requirement? For HW drivers, It is OK remove the particular requirement. But, If there is an issue(performance/functionality) for enabling such feature in SW driver. I would like keep that constraint to keep eventdev as abstraction for both SW and HW driver. Harry and/or Mattias.ronnblom can comment from SW driver perspective. > > -Matias