From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id EB419A04B4; Tue, 19 Nov 2019 13:12:48 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id ADCAFCF3; Tue, 19 Nov 2019 13:12:42 +0100 (CET) Received: from dispatch1-us1.ppe-hosted.com (dispatch1-us1.ppe-hosted.com [148.163.129.52]) by dpdk.org (Postfix) with ESMTP id 55C66271 for ; Tue, 19 Nov 2019 13:12:39 +0100 (CET) X-Virus-Scanned: Proofpoint Essentials engine Received: from webmail.solarflare.com (webmail.solarflare.com [12.187.104.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mx1-us1.ppe-hosted.com (PPE Hosted ESMTP Server) with ESMTPS id 93904100077; Tue, 19 Nov 2019 12:12:37 +0000 (UTC) Received: from ocex03.SolarFlarecom.com (10.20.40.36) by ocex03.SolarFlarecom.com (10.20.40.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 19 Nov 2019 04:12:35 -0800 Received: from opal.uk.solarflarecom.com (10.17.10.1) by ocex03.SolarFlarecom.com (10.20.40.36) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 19 Nov 2019 04:12:34 -0800 Received: from ukv-loginhost.uk.solarflarecom.com (ukv-loginhost.uk.solarflarecom.com [10.17.10.39]) by opal.uk.solarflarecom.com (8.13.8/8.13.8) with ESMTP id xAJCCXTi015155; Tue, 19 Nov 2019 12:12:33 GMT Received: from ukv-loginhost.uk.solarflarecom.com (localhost [127.0.0.1]) by ukv-loginhost.uk.solarflarecom.com (Postfix) with ESMTP id 76BA5161648; Tue, 19 Nov 2019 12:12:33 +0000 (GMT) From: Andrew Rybchenko To: Thomas Monjalon , Ferruh Yigit , Pavan Nikhilesh , "Neil Horman" , John McNamara , Marko Kovacevic CC: Date: Tue, 19 Nov 2019 12:12:14 +0000 Message-ID: <1574165536-2586-1-git-send-email-arybchenko@solarflare.com> X-Mailer: git-send-email 1.8.3.1 In-Reply-To: <1574165145-23960-1-git-send-email-arybchenko@solarflare.com> References: <1574165145-23960-1-git-send-email-arybchenko@solarflare.com> MIME-Version: 1.0 Content-Type: text/plain X-TM-AS-Product-Ver: SMEX-12.5.0.1300-8.5.1010-25050.005 X-TM-AS-Result: No-5.231400-4.000000-10 X-TMASE-MatchedRID: RoGFAXAsZ+BWUdWZNc/zWRIRh9wkXSlFJih/yo+OvlWRoQLwUmtovxxS cgjK3TZJ35oRU0iC50SPQi9XuOWoOKerivEziUtxcI7vRACwF0IGchEhVwJY3ygVbxW7FDOVNH2 M+0Uex9zMXMCgAgCo/gGgqRQZQsCiVHa5Ax0DhIiEv01fZOqaQLx2voUbwFB95kCVFHoAgnuSDd w9v34fhDa+bWYqf1uAU2yoXteGi/121zBthUokNZixDyZ4rnsHfS0Ip2eEHnz3IzXlXlpamPoLR 4+zsDTtLa13Fo3TPRYYQblXyWS6BwfafHqawJzmuVhzwgNj6+BR/RgxK4o8nFZca9RSYo/b X-TM-AS-User-Approved-Sender: No X-TM-AS-User-Blocked-Sender: No X-TMASE-Result: 10--5.231400-4.000000 X-TMASE-Version: SMEX-12.5.0.1300-8.5.1010-25050.005 X-MDID: 1574165558-CmO0amI5igv1 Subject: [dpdk-dev] [PATCH v2 1/3] ethdev: remove deprecation notice for packet type set 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" The functionality is added, but the deprecation notice is not removed. Fixes: 5d4813acda2c ("ethdev: add packet type range function") Signed-off-by: Andrew Rybchenko --- v2: - none doc/guides/rel_notes/deprecation.rst | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index f545801f6d..65076acb13 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -68,21 +68,6 @@ Deprecation Notices In 19.11 PMDs will still update the fields even when the offloads are not enabled. -* ethdev: New function ``rte_eth_dev_set_supported_ptypes`` will be added in - 19.11. - This will allow application to request PMD to set specific ptypes defined - through ``rte_eth_dev_set_supported_ptypes`` in ``rte_mbuf::packet_type``. - If application doesn't want any ptype information it can call - ``rte_eth_dev_set_supported_ptypes(ethdev_id, RTE_PTYPE_UNKNOWN)`` and PMD - will set ``rte_mbuf::packet_type`` to ``0``. - If application doesn't call ``rte_eth_dev_set_supported_ptypes`` PMD can - return ``rte_mbuf::packet_type`` with ``rte_eth_dev_get_supported_ptypes``. - If application is interested only in L2/L3 layer, it can inform the PMD - to update ``rte_mbuf::packet_type`` with L2/L3 ptype by calling - ``rte_eth_dev_set_supported_ptypes(ethdev_id, RTE_PTYPE_L2_MASK | RTE_PTYPE_L3_MASK)``. - This scheme will allow PMDs to avoid lookup to internal ptype table on Rx and - thereby improve Rx performance if application wishes do so. - * cryptodev: support for using IV with all sizes is added, J0 still can be used but only when IV length in following structs ``rte_crypto_auth_xform``, ``rte_crypto_aead_xform`` is set to zero. When IV length is greater or equal -- 2.17.1