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 0A698A0032; Wed, 13 Jul 2022 14:10:19 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id BDB944282D; Wed, 13 Jul 2022 14:10:18 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id A76CB4280D for ; Wed, 13 Jul 2022 14:10:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1657714217; 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=weECHWv6ruICzb/nu6oWizV1SnQctqYUlgJ8FjVU52c=; b=OJfR1YtqHDnwT3aT/LLvLmtu1vDmpzkbsfSanXDXUTS+nbaJc+D46WJjGW0jjYF9V9LMQr 5uVt/rcHeudGUK3ARuQ3IsFFQRGtt9rI+tNwkGuPJ7itL/L/pzZwFrkM6Nf2b7WKti/L8d 5WHv0tli0i6S21hiOxJGdKyILTGEnyk= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-65-2h-pP6PDMHCqjk1buliq7Q-1; Wed, 13 Jul 2022 08:10:12 -0400 X-MC-Unique: 2h-pP6PDMHCqjk1buliq7Q-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 9D7D11C004E6; Wed, 13 Jul 2022 12:10:11 +0000 (UTC) Received: from [10.39.208.14] (unknown [10.39.208.14]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 7C85A2026D07; Wed, 13 Jul 2022 12:10:09 +0000 (UTC) Message-ID: <80e13baf-643d-d2d3-0305-4db0f2a00dbd@redhat.com> Date: Wed, 13 Jul 2022 14:10:07 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH v2] doc: announce transition to vDPA device name function To: Thomas Monjalon , dev@dpdk.org Cc: david.marchand@redhat.com, andrew.rybchenko@oktetlabs.ru, chenbo.xia@intel.com, mdr@ashroe.eu, xiao.w.wang@intel.com, matan@nvidia.com, vsrivast@xilinx.com, ferruh.yigit@xilinx.com References: <20210518073441.2749096-1-thomas@monjalon.net> <20220712133610.4175033-1-thomas@monjalon.net> From: Maxime Coquelin In-Reply-To: <20220712133610.4175033-1-thomas@monjalon.net> 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 On 7/12/22 15:36, Thomas Monjalon wrote: > There is a layer violation in the vDPA API for getting the device name. > Instead of providing the name at vDPA level, > a function returns the low-level device object. > The plan is to introduce a new function in 22.11, promote in 23.07, > and remove rte_vdpa_get_rte_device() in 23.11. > > Signed-off-by: Thomas Monjalon > --- > v2: one year passed, update with a new plan > v1 was proposing a close function, only device name is needed > --- > doc/guides/rel_notes/deprecation.rst | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst > index 4e5b23c53d..0f7fefbf6a 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -107,6 +107,13 @@ Deprecation Notices > alternative is implemented. > The legacy actions should be removed in DPDK 22.11. > > +* vdpa: The vDPA API should not try to manipulate or export > + any ``rte_device`` object, which belongs to the bus layer. > + The function ``rte_vdpa_get_rte_device()`` will be deprecated in 23.07, > + when its usage will be replaced with ``rte_vdpa_get_device_name()``. > + The new function should enter in 22.11 and get promoted to stable in 23.07. > + The target is to remove ``rte_vdpa_get_rte_device()`` in 23.11. > + > * cryptodev: Hide structures ``rte_cryptodev_sym_session`` and > ``rte_cryptodev_asym_session`` to remove unnecessary indirection between > session and the private data of session. An opaque pointer can be exposed Acked-by: Maxime Coquelin Thanks, Maxime