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 67D45A053A; Tue, 4 Aug 2020 10:48:34 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A15C61C025; Tue, 4 Aug 2020 10:48:33 +0200 (CEST) Received: from us-smtp-1.mimecast.com (us-smtp-delivery-1.mimecast.com [207.211.31.120]) by dpdk.org (Postfix) with ESMTP id D4DD8255 for ; Tue, 4 Aug 2020 10:48:31 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1596530911; 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; bh=Aie8dXd9jJ6QbJvYe3MK2cUaZyvkjBCpyX/gHxI9L2w=; b=JekKsXDuyaPj4AiqsWruF7Dpn4bcVzjGZtso8ExuNkzWkIedA+eGGq3p9Jak0K56hleCI4 60y7LUShKdfp9t+y2qg9sKfhBvR7CucR2nubrNF8Yxb6txmSWTOye23Ccrqd77QNBlnQxE ToRVeHIJFUpsESxZlbteyYiasNSG9dA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-75-8IIM4dCnPzuogWRof3nlKA-1; Tue, 04 Aug 2020 04:48:27 -0400 X-MC-Unique: 8IIM4dCnPzuogWRof3nlKA-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A929F800404; Tue, 4 Aug 2020 08:48:26 +0000 (UTC) Received: from dmarchan.remote.csb (unknown [10.40.193.204]) by smtp.corp.redhat.com (Postfix) with ESMTP id 253205DA73; Tue, 4 Aug 2020 08:48:24 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: thomas@monjalon.net, dmitry.kozliuk@gmail.com, grive@u256.net Date: Tue, 4 Aug 2020 10:47:32 +0200 Message-Id: <20200804084732.882-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=david.marchand@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [PATCH] doc: announce PCI resources map API removal 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 PCI resources map API (pci_map_resource/pci_unmap_resource) was imposing use of Unix mmap flags while it does not make sense on Windows. This API was only used to internally setup PCI devices in the PCI bus driver and has no known external users. Announce its removal in 20.11 with its associated structures. The workaround implemented in the commit 9d2b24593724 ("pci: keep API compatibility with mmap values") will be removed at the same time. Signed-off-by: David Marchand --- 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 ea4cfa7a48..24808c002c 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -67,6 +67,17 @@ Deprecation Notices us extending existing enum/define. One solution can be using a fixed size array instead of ``.*MAX.*`` value. +* pci: The PCI resources map API (``pci_map_resource`` and + ``pci_unmap_resource``) was not abstracting the Unix mmap flags (see the + workaround for Windows support implemented in the commit + 9d2b24593724 ("pci: keep API compatibility with mmap values")). + This API will be removed from the public API in 20.11 and moved to the PCI + bus driver along with the PCI resources lists and associated structures + (``pci_map``, ``pci_msix_table``, ``mapped_pci_resource`` and + ``mapped_pci_res_list``). + With this removal, there won't be a need for the mentioned workaround which + will be reverted. + * ethdev: Split the ``struct eth_dev_ops`` struct to hide it as much as possible will be done in 20.11. Currently the ``struct eth_dev_ops`` struct is accessible by the application -- 2.23.0