From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 1A3C1A0557; Thu, 9 Jun 2022 09:54:15 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A92CE40689; Thu, 9 Jun 2022 09:54:14 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 2A5A640220 for ; Thu, 9 Jun 2022 09:54:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1654761252; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uZkwkjL58IdtAPP3Ji0fuPjPLIoD3QJ6A555p1xSU14=; b=P9g6mpFRSMEfxNxKRcSRToeTVHKcbPSkRhzgjg02gCTIJZFvCtP6GeR1vC/EdubZZH1VYF +9QW1fLQCXvHDYthPd/DJpDZF14/kQJaNFoEJlerZVh7kfHBHhX1afiALq/5bA7oc6zTOQ AkIxuBNhYBxpUS957HVNOJNEmmOJwNs= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-266-Y00GqvwUM2uy9ubUoMeN1g-1; Thu, 09 Jun 2022 03:54:08 -0400 X-MC-Unique: Y00GqvwUM2uy9ubUoMeN1g-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.rdu2.redhat.com [10.11.54.4]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A427B8339D0; Thu, 9 Jun 2022 07:54:02 +0000 (UTC) Received: from [10.39.208.20] (unknown [10.39.208.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id D3AEB2026985; Thu, 9 Jun 2022 07:54:00 +0000 (UTC) Message-ID: <4cf73c76-13fd-239f-8092-a4e034dab055@redhat.com> Date: Thu, 9 Jun 2022 09:53:58 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.9.0 Subject: Re: [PATCH v4] doc: announce changes in bbdev related to enum extension To: Nicolas Chautru , dev@dpdk.org, gakhil@marvell.com, thomas@monjalon.net Cc: trix@redhat.com, ray.kinsella@intel.com, bruce.richardson@intel.com, hemant.agrawal@nxp.com, david.marchand@redhat.com, stephen@networkplumber.org References: <1647542252-35727-2-git-send-email-nicolas.chautru@intel.com> <1654734870-131398-1-git-send-email-nicolas.chautru@intel.com> <1654734870-131398-2-git-send-email-nicolas.chautru@intel.com> From: Maxime Coquelin In-Reply-To: <1654734870-131398-2-git-send-email-nicolas.chautru@intel.com> X-Scanned-By: MIMEDefang 2.78 on 10.11.54.4 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=maxime.coquelin@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi Nicolas, On 6/9/22 02:34, Nicolas Chautru wrote: > 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 > --- > 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. Thanks for rewording the notice. Acked-by: Maxime Coquelin Maxime