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 3B864A0C46; Tue, 31 Aug 2021 15:21:45 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E81E24013F; Tue, 31 Aug 2021 15:21:44 +0200 (CEST) Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by mails.dpdk.org (Postfix) with ESMTP id 5FFEE40041 for ; Tue, 31 Aug 2021 15:21:43 +0200 (CEST) X-IronPort-AV: E=McAfee;i="6200,9189,10092"; a="216617828" X-IronPort-AV: E=Sophos;i="5.84,366,1620716400"; d="scan'208";a="216617828" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Aug 2021 06:21:42 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.84,366,1620716400"; d="scan'208";a="531096417" Received: from dpdk-xuanding-dev2.sh.intel.com ([10.67.119.115]) by FMSMGA003.fm.intel.com with ESMTP; 31 Aug 2021 06:21:40 -0700 From: Xuan Ding To: dev@dpdk.org, anatoly.burakov@intel.com Cc: maxime.coquelin@redhat.com, chenbo.xia@intel.com, ferruh.yigit@intel.com, jiayu.hu@intel.com, bruce.richardson@intel.com, Xuan Ding Date: Tue, 31 Aug 2021 13:10:39 +0000 Message-Id: <20210831131039.29964-1-xuan.ding@intel.com> X-Mailer: git-send-email 2.17.1 Subject: [dpdk-dev] [PATCH] doc: announce change in vfio dma mapping 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 Sender: "dev" Currently, the VFIO subsystem will compact adjacent DMA regions for the purposes of saving space in the internal list of mappings. This has a side effect of compacting two separate mappings that just happen to be adjacent in memory. Since VFIO implementation on IA platforms also does not allow partial unmapping of memory mapped for DMA, the current DPDK VFIO implementation will prevent unmapping of accidentally adjacent maps even though it could have been unmapped [1]. The proper fix for this issue is to change the VFIO DMA mapping API to also include page size, and always map memory page-by-page. [1] https://mails.dpdk.org/archives/dev/2021-July/213493.html Signed-off-by: Xuan Ding --- doc/guides/rel_notes/deprecation.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 76a4abfd6b..1234420caf 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -287,3 +287,6 @@ Deprecation Notices reserved bytes to 2 (from 3), and use 1 byte to indicate warnings and other information from the crypto/security operation. This field will be used to communicate events such as soft expiry with IPsec in lookaside mode. + +* vfio: the functions `rte_vfio_container_dma_map` will be amended to + include page size. This change is targeted for DPDK 22.02. -- 2.17.1