From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0105CA0545; Tue, 28 Jun 2022 15:55:52 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DA9C940691; Tue, 28 Jun 2022 15:55:52 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by mails.dpdk.org (Postfix) with ESMTP id 0E4A7400D7 for <dev@dpdk.org>; Tue, 28 Jun 2022 15:55:50 +0200 (CEST) Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 25SAHiWh010854; Tue, 28 Jun 2022 06:53:46 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding : content-type; s=pfpt0220; bh=Zvnl12+ty6sCWndYstpV6ZYMtAgoJI5hD3wT1fNGi6k=; b=A1RaAKmspHRv0nXoj8wWedByhXzlvFuwNSENiXRJzaRXdE/2Uqo9qlhob6OsA+8l+3Mg v0edWmTqsamWNy44ONgwghg7Z2dzKJCXynqxC3edGPmh8EaslQoMkm3m+AN8ShDMEUGL 56mSufyXOczXOyHJ6phtE4kV2u+POq0q0oTdim6GrBM+BU+TiAJu1dv7Rzx5XhORsubl 7CCieKxirXLj/SBYJnfCafITyDCFi8PdpzoP696w+3At0LlZnF7w1UMAT2S68zAodoPw IrvFKsm+BjJ2jZzaoiCp0uwmvYPjF3Z58S5i95SMJBUiPYmzh+p6i44Ith9QFVzb7pdO 2Q== Received: from dc5-exch02.marvell.com ([199.233.59.182]) by mx0b-0016f401.pphosted.com (PPS) with ESMTPS id 3gx1vm40g0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 28 Jun 2022 06:53:46 -0700 Received: from DC5-EXCH02.marvell.com (10.69.176.39) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server (TLS) id 15.0.1497.18; Tue, 28 Jun 2022 06:53:44 -0700 Received: from maili.marvell.com (10.69.176.80) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server id 15.0.1497.18 via Frontend Transport; Tue, 28 Jun 2022 06:53:44 -0700 Received: from localhost.localdomain (unknown [10.28.34.25]) by maili.marvell.com (Postfix) with ESMTP id 7296A3F7093; Tue, 28 Jun 2022 06:53:43 -0700 (PDT) From: <skori@marvell.com> To: Ray Kinsella <mdr@ashroe.eu> CC: <dev@dpdk.org>, Sunil Kumar Kori <skori@marvell.com> Subject: [PATCH 1/2] doc: announce region based device mapping support Date: Tue, 28 Jun 2022 19:23:38 +0530 Message-ID: <20220628135339.2882914-1-skori@marvell.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-ORIG-GUID: IL8y0hHo2gZER3XWs9YbGtnagqt_QAV_ X-Proofpoint-GUID: IL8y0hHo2gZER3XWs9YbGtnagqt_QAV_ X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.883,Hydra:6.0.517,FMLib:17.11.122.1 definitions=2022-06-28_07,2022-06-28_01,2022-06-22_01 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org From: Sunil Kumar Kori <skori@marvell.com> Adding region based device mapping support, which enables pci device to map only required memory region instead of mapping full BAR. Signed-off-by: Sunil Kumar Kori <skori@marvell.com> --- doc/guides/rel_notes/deprecation.rst | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 4e5b23c53d..8800a3eb41 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -125,3 +125,16 @@ Deprecation Notices applications should be updated to use the ``dmadev`` library instead, with the underlying HW-functionality being provided by the ``ioat`` or ``idxd`` dma drivers + +* pci: Update ``rte_pci_device`` and ``rte_pci_driver`` to add region based + memory mapping support. There could be a requirement to mmap specific memory + region only. Using this mechanism, pci device can be mapped for + a given BAR at a given offset of given size. + + ``rte_pci_device`` will be added with following field + ``regions[PCI_MAX_RESOURCE][PCI_MAX_REGION_PER_RESOURCE];``. This field will + specify the regions which are mapped for a given BAR. + + ``rte_pci_driver`` will be added with ``rte_pci_region_map *regions`` and + ``valid_bars[PCI_MAX_RESOURCE]``. Using these fields, driver can propagate + its region information which are required to be mmap. -- 2.25.1