From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id 76D601C153 for ; Thu, 12 Apr 2018 18:24:36 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Apr 2018 09:24:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,442,1517904000"; d="scan'208";a="216111941" Received: from aburakov-mobl.ger.corp.intel.com (HELO [10.237.220.128]) ([10.237.220.128]) by orsmga005.jf.intel.com with ESMTP; 12 Apr 2018 09:24:26 -0700 To: "Wang, Xiao W" , "Yigit, Ferruh" Cc: "dev@dpdk.org" , "maxime.coquelin@redhat.com" , "Wang, Zhihong" , "Bie, Tiwei" , "Tan, Jianfeng" , "Liang, Cunming" , "Daly, Dan" , "thomas@monjalon.net" , "gaetan.rivet@6wind.com" , "hemant.agrawal@nxp.com" , "Chen, Junjie J" References: <20180405180701.16853-4-xiao.w.wang@intel.com> <20180412071956.66178-1-xiao.w.wang@intel.com> <20180412071956.66178-2-xiao.w.wang@intel.com> <974c9cd0-87c4-6ab1-0787-9278a7379fda@intel.com> From: "Burakov, Anatoly" Message-ID: <36187714-3454-38ee-1836-204790d93e10@intel.com> Date: Thu, 12 Apr 2018 17:24:25 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v6 1/4] eal/vfio: add multiple container support 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: , X-List-Received-Date: Thu, 12 Apr 2018 16:24:37 -0000 On 12-Apr-18 5:07 PM, Wang, Xiao W wrote: > Hi Anatoly, > <...> >> >> Also, why providing DMA type? There's already a VFIO type pointer in >> vfio_config - you can set this pointer for every new created container, >> so the user wouldn't have to care about IOMMU type. Is it not possible >> to figure out DMA type from within EAL VFIO? If not, maybe provide an >> API to do so, e.g. rte_vfio_container_set_dma_type()? > > It's possible, EAL VFIO should be able to figure out a container's DMA type. You probably won't be able to do it until you add a group into the container, so probably best place to do it would be on group_bind? -- Thanks, Anatoly