From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id DDB3C271 for ; Thu, 30 Nov 2017 05:20:48 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Nov 2017 20:20:47 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.45,339,1508828400"; d="scan'208";a="1250152199" Received: from txasoft-yocto.an.intel.com (HELO txasoft-yocto.an.intel.com.) ([10.123.72.111]) by fmsmga002.fm.intel.com with ESMTP; 29 Nov 2017 20:20:47 -0800 From: Gage Eads To: dev@dpdk.org Cc: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com, bruce.richardson@intel.com, hemant.agrawal@nxp.com, nipun.gupta@nxp.com, santosh.shukla@caviumnetworks.com Date: Wed, 29 Nov 2017 22:20:34 -0600 Message-Id: <1512015636-31878-1-git-send-email-gage.eads@intel.com> X-Mailer: git-send-email 2.7.4 Subject: [dpdk-dev] [PATCH 0/2] add implicit release disable capability 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, 30 Nov 2017 04:20:49 -0000 This patch set introduces an event device capability for disabling implicit release -- in which rte_event_dequeue_burst() releases any unreleased, previously dequeued events -- on a per-port basis. The port configuration struct is likewise extended with a disable_implicit_release option, for PMDs that support the capability. If the option is set for a port, the application is responsible for releasing the port's dequeued events (either with RTE_EVENT_OP_RELEASE or RTE_EVENT_OP_FORWARD). This behavior was previously discussed (http://dpdk.org/ml/archives/dev/2017-November/081037.html) as a way to avoid flow migration problems when using eventdev with look-aside hardware (such as cryptodev). For instance, if each worker puts dequeued events in a per-worker crypto request queue and periodically polls the response queue to forward the packets, it shouldn't release the events until the crypto operation completes. By disabling the implicit release, it can dequeue further events and process them while the crypto operation(s) execute in parallel. The only PMD that supports this capability is the sw PMD. For all PMDs, the default port configuration is implicit releases enabled. The second patch in the series isn't directly related to implicit release, but the code changes depend on the first patch. Gage Eads (2): eventdev: add implicit release disable capability event/sw: simplify credit scheme drivers/event/dpaa2/dpaa2_eventdev.c | 2 ++ drivers/event/octeontx/ssovf_evdev.c | 1 + drivers/event/skeleton/skeleton_eventdev.c | 1 + drivers/event/sw/sw_evdev.c | 10 +++++--- drivers/event/sw/sw_evdev.h | 1 + drivers/event/sw/sw_evdev_worker.c | 38 +++++++++++++++--------------- examples/eventdev_pipeline_sw_pmd/main.c | 24 ++++++++++++++++++- lib/librte_eventdev/rte_eventdev.c | 9 +++++++ lib/librte_eventdev/rte_eventdev.h | 23 +++++++++++++++--- test/test/test_eventdev.c | 9 +++++++ test/test/test_eventdev_sw.c | 20 ++++++++++++++-- 11 files changed, 110 insertions(+), 28 deletions(-) -- 2.7.4