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 0BB38A0032; Tue, 12 Jul 2022 15:36:22 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 8F72541109; Tue, 12 Jul 2022 15:36:21 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 384FA400D4 for ; Tue, 12 Jul 2022 15:36:20 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 5BF235C00CE; Tue, 12 Jul 2022 09:36:19 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 12 Jul 2022 09:36:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1657632979; x=1657719379; bh=no 3ajvNjOuq2/fFdOUm9fZ7c3z01qZtF3uSF0M9OHUY=; b=tkNNlNPSK6tYJlVAsx RTDT37Lj2+RwqMZoi2kgXmqizf6BlBhV71bGFVh6XXNcxSGTMAXFxIQgeJEiqdnl dGBrn8vVaxYVweKcumt8zxqWmH6miX+eAR1IxEKXIcM3lSWm+QclfXbd/CSJZIsp VlnbkU/DPoMIQ1ghVW0Kk2jsns6Y4S4iKwhnKnM33YB+0zlsvMFUqgIne/YRkTey i39aFoxOSodVnoRr8yE4cEiw9E4PhwOzIoWd2362ttGEfH/yMU98w3aoNguJs2tL iak9dlzb9N1mz2/nBTML9tx1MJpyuipJHFX558OtMinxxlP0MGMmK4fWBc880ThM IpnQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1657632979; x=1657719379; bh=no3ajvNjOuq2/ fFdOUm9fZ7c3z01qZtF3uSF0M9OHUY=; b=gC5rrctANa7MTqbu/W+eOldnfoPTg 39jhefdbw8f2JySASoJ6xXOpIXGNSOCzog1JUclOc+UvnTRwIRm/BUSM0fVTpsn1 HzACb/tXUaOeBs4Dt4faxrasZaQplMyDBB7eEMvvAFm35lCebSRkjitlw5/iQ77A bDElit1ScOTIkoAA1mmBL1hfYKz6h07XF6EJoHskYINFiAdOU2p5N1SfGMqzRgYs rAyuLBzJ5j7s+2OEysWQaw/OOTXvvcJZuaBs340zy+1Oa6kmWXSXZhc4SH106x/k aaebWeo5buwcYNXb5oF2gTdZXgbTRJG7vsoCE85qOFOviPS9vrmli7pcA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudejhedgieejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkffojghfggfgsedtke ertdertddtnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepvdejhfdugeehvddtie ejieegteeuudfgjeeukeeiledthfetveekhefhieelhfdtnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Jul 2022 09:36:17 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: david.marchand@redhat.com, andrew.rybchenko@oktetlabs.ru, maxime.coquelin@redhat.com, chenbo.xia@intel.com, mdr@ashroe.eu, xiao.w.wang@intel.com, matan@nvidia.com, vsrivast@xilinx.com, ferruh.yigit@xilinx.com Subject: [PATCH v2] doc: announce transition to vDPA device name function Date: Tue, 12 Jul 2022 15:36:10 +0200 Message-Id: <20220712133610.4175033-1-thomas@monjalon.net> X-Mailer: git-send-email 2.36.1 In-Reply-To: <20210518073441.2749096-1-thomas@monjalon.net> References: <20210518073441.2749096-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 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 -- 2.36.1