From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id EB3F2A0550; Thu, 9 Jun 2022 02:45:19 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 25A3A4113F; Thu, 9 Jun 2022 02:45:16 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by mails.dpdk.org (Postfix) with ESMTP id 3AD3640220 for <dev@dpdk.org>; Thu, 9 Jun 2022 02:45:14 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654735514; x=1686271514; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=qmoqIE/oCc01Pt1/aNZ5V6VbMGhNuE+Abe4bG2ypp2k=; b=Wxw7FBVxu7bO6K8G+8raSQUphGTwnLuvZcCxBkrjlfKwKV8qt8KPDOO3 usNjr/vrJV55WAsAFF3gT1ulMA4soUwk1EBd8n9cQAP59Cm86yYoLqJki frWajfnoHBCsczyLjnb/eiwK/E4Bf9GsieRlcJg7mfjJZc0hMr82hlIN3 P6G6eVqPL52EpU7QF+nqNFIvDR5Lf6o1KnGleTPm6U2E5rFOUkKlMU9ov gkgwTdTtjsPI26NPYpIINLPGo8ZGgvI+t6eSkCyUYoOxDarFi0Daox/t9 ZRs+0bKtCaRj0eCZbTh1CYpD93fVFr/jf7INP1kcrKHvsiVvBAMbTru+H Q==; X-IronPort-AV: E=McAfee;i="6400,9594,10372"; a="260235709" X-IronPort-AV: E=Sophos;i="5.91,287,1647327600"; d="scan'208";a="260235709" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jun 2022 17:45:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.91,287,1647327600"; d="scan'208";a="683662078" Received: from skx-5gnr-sc12-4.sc.intel.com ([172.25.69.210]) by fmsmga002.fm.intel.com with ESMTP; 08 Jun 2022 17:45:11 -0700 From: Nicolas Chautru <nicolas.chautru@intel.com> To: dev@dpdk.org, gakhil@marvell.com, thomas@monjalon.net, maxime.coquelin@redhat.com Cc: trix@redhat.com, ray.kinsella@intel.com, bruce.richardson@intel.com, hemant.agrawal@nxp.com, david.marchand@redhat.com, stephen@networkplumber.org, Nicolas Chautru <nicolas.chautru@intel.com> Subject: [PATCH v4] doc: announce changes in bbdev related to enum extension Date: Wed, 8 Jun 2022 17:34:30 -0700 Message-Id: <1654734870-131398-2-git-send-email-nicolas.chautru@intel.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1654734870-131398-1-git-send-email-nicolas.chautru@intel.com> References: <1647542252-35727-2-git-send-email-nicolas.chautru@intel.com> <1654734870-131398-1-git-send-email-nicolas.chautru@intel.com> X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Intent to resolve in DPDK 22.11 historical usage which prevents graceful extension of enum and API without troublesome ABI breakage as well as extending API RTE_BBDEV_OP_FFT for new operation type in bbdev as well as other new members in existing structures. Signed-off-by: Nicolas Chautru <nicolas.chautru@intel.com> --- doc/guides/rel_notes/deprecation.rst | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 4e5b23c..c8ab1ec 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -112,6 +112,17 @@ Deprecation Notices session and the private data of session. An opaque pointer can be exposed directly to application which can be attached to the ``rte_crypto_op``. +* bbdev: ``RTE_BBDEV_OP_TYPE_COUNT`` terminating the ``rte_bbdev_op_type`` + enum will be deprecated and instead use fixed array size when required to allow for + future enum extension. + Will extend API to support new operation type ``RTE_BBDEV_OP_FFT`` as per this + RFC https://patchwork.dpdk.org/project/dpdk/list/?series=22111 + New members will be added in ``rte_bbdev_driver_info`` to expose PMD queue topology inspired + by this RFC https://patches.dpdk.org/project/dpdk/list/?series=22076 + New member will be added in ``rte_bbdev_driver_info`` to expose the device status as per + this RFC https://patches.dpdk.org/project/dpdk/list/?series=23367 + This should be updated in DPDK 22.11. + * security: Hide structure ``rte_security_session`` and expose an opaque pointer for the private data to the application which can be attached to the packet while enqueuing. -- 1.8.3.1