From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-8.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E0D2C43463 for ; Mon, 21 Sep 2020 13:05:59 +0000 (UTC) Received: from dpdk.org (dpdk.org [92.243.14.124]) by mail.kernel.org (Postfix) with ESMTP id 140E620BED for ; Mon, 21 Sep 2020 13:05:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 140E620BED Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=intel.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dev-bounces@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9AE361D8E9; Mon, 21 Sep 2020 15:05:57 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 56D3E1D702 for ; Mon, 21 Sep 2020 15:05:55 +0200 (CEST) IronPort-SDR: 5CV8thX1OrKxrCwyExpjBMrkTBQH8CCKdx0jXw7TbhJoODtkhWO33yG2bqAtvWupBn5fH40F+c st8w0ed+fibg== X-IronPort-AV: E=McAfee;i="6000,8403,9750"; a="161294776" X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="161294776" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 06:04:16 -0700 IronPort-SDR: qFW9v+nUIKYVmqlxXOQ9WX/6zHY09C2RpAKdk6xl5Jnmra9FeKLG7NSYjmmmuoNXo4TzwYgFSt 8IpA/dxeIVOQ== X-IronPort-AV: E=Sophos;i="5.77,286,1596524400"; d="scan'208";a="485447503" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.213.248.121]) ([10.213.248.121]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 21 Sep 2020 06:04:14 -0700 To: wangyunjian , dev@dpdk.org, zhihong.wang@intel.com Cc: jerry.lilijun@huawei.com, xudingke@huawei.com References: <1589540514-26972-1-git-send-email-wangyunjian@huawei.com> From: "Burakov, Anatoly" Message-ID: <93be7654-c798-f8b3-bb68-512b61a8ac6e@intel.com> Date: Mon, 21 Sep 2020 14:04:12 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <1589540514-26972-1-git-send-email-wangyunjian@huawei.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] vfio: change default per vfio_cfg map all dpdk segments for DMA 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" On 15-May-20 12:01 PM, wangyunjian wrote: > From: Yunjian Wang > > As all vfio_cfgs need to map all dpdk segments for DMA, but now only > default_vfio_cfg map it. This patch changes rte_vfio_setup_device() > as a default map, so that IOMMU progrming does notneed to map dpdk > segments separately. > > Signed-off-by: Yunjian Wang > --- I'm pretty sure this was intentional. The other containers were supposed to call DMA maps manually. That said, i would probably ask the original submitter for the multi-container feature as i have only a vague idea of usages for this API. +Zhihong, as that's the closest i could find to a maintainer for this functionality :) -- Thanks, Anatoly