From patchwork Thu Jul 2 22:13:57 2020 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Timothy McDaniel X-Patchwork-Id: 72865 X-Patchwork-Delegate: thomas@monjalon.net Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id B3A99A0519; Fri, 3 Jul 2020 00:16:07 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 525051D6A8; Fri, 3 Jul 2020 00:16:07 +0200 (CEST) Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 8DFD61D5CE for ; Fri, 3 Jul 2020 00:16:05 +0200 (CEST) IronPort-SDR: +6qiGZ2+EliurMOFCVqNUIiCqdqZC9Zm4HktkxSWFs1WhgF4c9aiA3j27E12ziSMBrM/iKp/bk I7bQ7eqqGDXw== X-IronPort-AV: E=McAfee;i="6000,8403,9670"; a="145187149" X-IronPort-AV: E=Sophos;i="5.75,305,1589266800"; d="scan'208";a="145187149" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Jul 2020 15:16:04 -0700 IronPort-SDR: 1joy6rsyeTTeWSmWKmXAq+FfqYgpxJzvSmzKnd2A6schB4mRqICLIBEqd+DKUCkgul0cWpvN7s dDbKpECWLmog== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.75,305,1589266800"; d="scan'208";a="321640360" Received: from txasoft-yocto.an.intel.com ([10.123.72.192]) by FMSMGA003.fm.intel.com with ESMTP; 02 Jul 2020 15:16:03 -0700 From: "McDaniel, Timothy" To: dev@dpdk.org Cc: jerinj@marvell.com, gage.eads@intel.com, harry.van.haaren@intel.com, mdr@ashroe.eu, nhorman@tuxdriver.com, nikhil.rao@intel.com, erik.g.carrillo@intel.com, abhinandan.gujjar@intel.com, pbhagavatula@marvell.com, hemant.agrawal@nxp.com, mattias.ronnblom@ericsson.com, peter.mccarthy@intel.com, "McDaniel, Timothy" Date: Thu, 2 Jul 2020 17:13:57 -0500 Message-Id: <1593728037-15717-1-git-send-email-timothy.mcdaniel@intel.com> X-Mailer: git-send-email 1.7.10 Subject: [dpdk-dev] [PATCH] doc: announce changes to eventdev public data structures 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" From: "McDaniel, Timothy" Signed-off-by: McDaniel, Timothy --- doc/guides/rel_notes/deprecation.rst | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index d1034f6..6af9b40 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -130,3 +130,31 @@ Deprecation Notices Python 2 support will be completely removed in 20.11. In 20.08, explicit deprecation warnings will be displayed when running scripts with Python 2. + +* eventdev: Three public data structures will be updated in 20.11; + ``rte_event_dev_info``, ``rte_event_dev_config``, and + ``rte_event_port_conf``. + Two new members will be added to the ``rte_event_dev_info`` struct. + The first, max_event_port_links, will be a uint8_t, and represents the + maximum number of queues that can be linked to a single event port by + this device. The second, max_single_link_event_port_queue_pairs, will be a + uint8_t, and represents the maximum number of event ports and queues that + are optimized for (and only capable of) single-link configurations + supported by this device. These ports and queues are not accounted for in + max_event_ports or max_event_queues. + One new member will be added to the ``rte_event_dev_config`` struct. The + nb_single_link_event_port_queues member will be a uint8_t, and will + represent the number of event ports and queues that will be singly-linked + to each other. These are a subset of the overall event ports and queues. + This value cannot exceed nb_event_ports or nb_event_queues. If the + device has ports and queues that are optimized for single-link usage, this + field is a hint for how many to allocate; otherwise, regular event ports and + queues can be used. + Finally, the ``rte_event_port_conf`` struct will be + modified as follows. The uint8_t implicit_release_disabled field + will be replaced by a uint32_t event_port_cfg field. The new field will + initially have two bits assigned. RTE_EVENT_PORT_CFG_DISABLE_IMPL_REL + will have the same meaning as implicit_release_disabled. The second bit, + RTE_EVENT_PORT_CFG_SINGLE_LINK will be set if the event port links only + to a single event queue. +